On Sat, 2005-06-11 at 10:39 +0200, Danilo Šegan wrote: > Hi Carlos, Hi > > Yesterday at 20:46, Carlos Perelló Marín wrote: > > > I can tell you that we are developing a script in Ubuntu to get > > translations from GNOME's CVS into our system so we will get all updates > > after release as we provide translation updates after release. That > > means that any translation added to GNOME a 2.x release will be used in > > Ubuntu. Of course, my opinion is that after last minor release from > > GNOME, you should give preference to next major GNOME release. > > What are you going to do with string freeze breakages? I.e. if you > ship a tarball which has "_Borwse", and it's later fixed in CVS and > translations are updated, this is going to end up untranslated, right? Not really, as our .pot files will not get that string breakage, the old translation will remain. > > Following the schedule goes three ways: it helps maintainers, it helps > translators and it helps distributors. True, and that's what I tried to explain, not sure if it was not clear enough. > > > So for instance, my recommendation is that, after 2.10.3 is released, > > you should concentrate on 2.11 and take care of the 2.10 branches only > > after you have 2.11 in a good status. > > Current roadmap[1] lists nothing but 2.10.1 which has already been > released. As Vicent says, I don't think we are not going to stay with 2.10.1... We had three minor releases until now and I didn't see anything that makes me think it's going to change now, but I could be wrong, of course. > > Cheers, > Danilo Cheers. > > [1]htt p://live.gnome.org/ReleasePlanning_2fTwoPointEleven > _______________________________________________ > gnome-i18n mailing list > gnome-i18n gnome org > http://mail.gnome.org/mailman/listinfo/gnome-i18n -- Carlos Perelló Marín Ubuntu Hoary (PowerPC) => http://www.ubuntulinux.org Linux Registered User #121232 mailto:carlos pemas net || mailto:carlos gnome org http://carlos.pemas.net Valencia - Spain
Attachment:
signature.asc
Description: This is a digitally signed message part