Quoting Olivier Berger ([EMAIL PROTECTED]): > I guess that if you provide a 4.2 package soon, at the same time as the > patch for 4.1.2 is prepared, uploading by your sponsor should be > coordinated with Christian Perrier's one, to avoir locking each-other. > I'd propose 4.1.2-3.2 to be going to testing/testing-security real fast > (via unstable), and 4.2 be kept in experimental in the meantime maybe...
That sounds to be a good plan. Having the "polished" 4.1.* version go its way through testing and then have 4.2 follow the same way. (if 4.2 introduce changes tha impact debconf l10n, we could even do a translation update round for it even while it is sitting in experimental). So, to summarize: - Olivier polishes 4.1.2-3.2 (ou -4 depeds on whether this is still considered an NMU or not), including debconf templates wording - He sends me at least the templates file and the full patch to Sven - I post a call for translation for 4.1.2 - translators have 10 days to update - I summarize translator's work (usually with a big tarball of debian/po as I check every incoming PO file) - Olivier prepares 4.1.2-3.2 (or -4) with that - I sponsor it While I work on 4.1.2 l10n, Sven adopts Olivier's changes and prepares a 4.2 upload. If that needs changes to debconf templates, we review them and I send *another* call for translation updates juste after the above 10 days delay (so that translations sent for 4.1 can be reused as a basis for 4.2). Then, summary and upload to experimental (I can sponsor here, again). And, once 4.1 reaches testing, you guys can upload 4.2 to unstable.
signature.asc
Description: Digital signature
