On Mon, Sep 27, 2004 at 08:03:49PM +0200, Alexander Sack wrote: > I think, that this would not be too hard to implement. On the other > hand, there would still be problems that some translations might not be > ready if mozilla* packages become ready to go in. IMHO, doing so looks like > a trick to declare translations not to be release critical and in fact > inferior to normal packages. That's hardly an issue, you just drop the translation (or ship an empty translation) until such a time that there is one. Since you are building all the translations from the same source it's easier to have them in sync with the mozilla packages so instead of: 1.- A new version of mozilla is uploaded to the archive 2.- New versions are uploaded to the archive, but not every package maintainer can cope up 3.- Mozilla cannot get into testing after the dealy because of 2) 4.- Somebody sends "uninstallable" RC bugs to sid because of 2) 5.- The packages that did not have an updated installation are removed from testing so that Mozilla can go in We could have: 1.- A new version of mozilla is uploaded 2.- A new version of the mozilla translations is uploaded 3.- Mozilla goes into testing after the delay (all translations are for the new version) together with the new version of mozilla-i18n and available translations. 4.- Updates to mozilla-i18n adding updated translations are moved into the archive For some time (until all translations are updated) you have a version in sid and testing which do not include all translations but that's better than having RC bugs (in either mozilla or the translation) because of it not being up-to-date, after all, it _will_ be removed because of this in the future. Regards Javier
Attachment:
signature.asc
Description: Digital signature