This one time, at band camp, Christian Perrier said:> > Working on this, I also updated the Spanish translation header so that > you can at least contact the language team list. > > Attached is the new doc/po4a/po directory.This doesn''t appear to be attached. Did you forget, or did mailman eat your attachment?> I would recommend a two-shot approach: > > -first call for updates only, with a short deadline (say 4 days) > -calls for new translations with a long deadline like 20 days > -in 5 days, upload the new version with fixed translations > request it to enter testing when ready > -in 20 days, when the first upload will have entered testing, then > upload a new one with new translations and hope that it will make the > releasThis sounds good. Thanks for the help, as always, -- ----------------------------------------------------------------- | ,''''`. Stephen Gran | | : :'' : sgran@debian.org | | `. `'' Debian user, admin, and developer | | `- http://www.debian.org | ----------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/adduser-devel/attachments/20070227/ddb383ce/attachment.pgp
> > Attached is the new doc/po4a/po directory. > > This doesn''t appear to be attached. Did you forget, or did mailman eat > your attachment?Just forgot, as often..:) -- -------------- next part -------------- A non-text attachment was scrubbed... Name: adduser-man.tar.gz Type: application/octet-stream Size: 196702 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/adduser-devel/attachments/20070227/1597bf13/adduser-man.tar-0001.obj
> > I would recommend a two-shot approach: > > > > -first call for updates only, with a short deadline (say 4 days) > > -calls for new translations with a long deadline like 20 days > > -in 5 days, upload the new version with fixed translations > > request it to enter testing when ready > > -in 20 days, when the first upload will have entered testing, then > > upload a new one with new translations and hope that it will make the > > releas > > This sounds good. Thanks for the help, as always,Ah, something I forgot: I''ll have a look at translations that come in to just check they''re correct. If I don''t followup, they''re correct, otherwise, I''ll answer to the bug report and the translator. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/adduser-devel/attachments/20070228/e002f920/attachment.pgp
> > -first call for updates only, with a short deadline (say 4 days) > > -calls for new translations with a long deadline like 20 days > > -in 5 days, upload the new version with fixed translations > > request it to enter testing when ready > > -in 20 days, when the first upload will have entered testing, then > > upload a new one with new translations and hope that it will make the > > releas > > This sounds good. Thanks for the help, as always,OK, I sent all call for updates: -3 call for existing translations updates to existing translators, giving them March 3rd 23:59UTC as deadline That means you can plan the upload for March 4th -3 call for new translations, in debian-i18n, with March 15th as deadline (this assumes that the former version went to testing), thus an upload an 16th. That one can make it to etch only if we don''t release before March 26th. Pretty unsure, but we''ll see anyway. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/adduser-devel/attachments/20070228/c2b00912/attachment.pgp
This one time, at band camp, Christian Perrier said:> OK, I sent all call for updates: > > -3 call for existing translations updates to existing translators, > giving them March 3rd 23:59UTC as deadline > That means you can plan the upload for March 4th > > -3 call for new translations, in debian-i18n, with March 15th as > deadline (this assumes that the former version went to testing), thus > an upload an 16th. That one can make it to etch only if we don''t > release before March 26th. Pretty unsure, but we''ll see anyway.This one time, at band camp, Christian Perrier said:> > Ah, something I forgot: I''ll have a look at translations that come in > to just check they''re correct. If I don''t followup, they''re correct, > otherwise, I''ll answer to the bug report and the translator.Thank you very much, Christian! That''s amazingly helpful. It was on my list to do for today, but I''m still fairly sick from FOSDEM, and I haven''t gotten to it yet. -- ----------------------------------------------------------------- | ,''''`. Stephen Gran | | : :'' : sgran@debian.org | | `. `'' Debian user, admin, and developer | | `- http://www.debian.org | ----------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/adduser-devel/attachments/20070228/604c5aa7/attachment.pgp
(wide CC list, sorry...) Stephen pinged me on IRC about changes to man pages, in the package''s SVN. I had a look at them and, indeed, when rebuilding the package, the PO files in doc/po4a/po are fuzzied. With po4a, this is not a so big deal as fuzzy strings will be incorporated in the generated man pages, in English. However, a short call for translation updates could be fine. Working on this, I also updated the Spanish translation header so that you can at least contact the language team list. Attached is the new doc/po4a/po directory. I suggest committing it to SVN and then run, from the doc/po4a/po/ directory: podebconf-report-po --podir=. --deadline="whataver deadline you want to set" ....which will post a call for translation updates to existing translators. You can also do: podebconf-report-po --call --podir=. --deadline="whataver deadline you want to set" ....which will post a call for *new* translations to debian-i18n While you''re at it, you can also get updates for the programs translations (it seems that 1 string is fuzzied) by just doing the same from the toplevel po/ directory And, of course, you can finish with debian/po...:-) I would recommend a two-shot approach: -first call for updates only, with a short deadline (say 4 days) -calls for new translations with a long deadline like 20 days -in 5 days, upload the new version with fixed translations request it to enter testing when ready -in 20 days, when the first upload will have entered testing, then upload a new one with new translations and hope that it will make the releas -- _______________________________________________ Adduser-devel mailing list Adduser-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/adduser-devel