> Well, it does. I told you about a note I wanted to add about possible > data loss if a user expects the old broken behavior. You even suggested > that I use the NEWS.Debian file instead (and I did not like the idea). > You should (if you have some time) have a look at the isync package in > experimental. I should probably have my new template reviewed by the > debian-l10n-english team before it is translated. > > I asked the release manager if I could upload this to unstable (and > hopefully let it reach etch) and Steve replied it was alright. So I may > soon upload to unstable.
In such case, the best, imho, is to sync your upload in unstable with
the result of the NMU campaign. The deadline I gave to translators is
Thursday December 1st.
What I suggest as schedule is:
-wait until Dec 1st
-I send you debian/po from my NMU
-you put the PO files in your tree *with* the new note
-you run debconf-udpatepo
-there you have two choices:
1) you upload and you send a call for l10n updates for another
round of upload that could last for the 10 days delay needed
for the package to migrate to testing
2) you first send a call for updates, giving only a few days delay
to translators and then upload the new release
Even though it is Not Good to bet on etch release delays, I think that
all this gives you enough time.
In both cases, I will not send a NMU anyway.
signature.asc
Description: Digital signature
