Le jeudi 03 juin 2010 à 10:24 +0200, Eugen Dedu a écrit : > On 03/06/10 07:18, Claude Paroz wrote: > > Le jeudi 03 juin 2010 à 06:45 +0200, Eugen Dedu a écrit : > >> On 02/06/10 22:02, Claude Paroz wrote: > >>> Le mercredi 02 juin 2010 à 17:39 +0000, GNOME Status Pages a écrit : > >>>> This is an automatic notification from status generation scripts on: > >>>> http://l10n.gnome.org. > >>>> > >>>> There have been following string additions to module 'ekiga.master': > >>>> > >>>> + "0: 56kbps, 1: ISDN, 2: DSL128, 3: DSL512, 4: LAN, 5: Custom" > >>>> + "Kind of network selected in the assistant" > >>>> > >>>> Note that this doesn't directly indicate a string freeze break, but it > >>>> might be worth investigating. > >>>> _______________________________________________ > >>> > >>> Hi Eugen, > >>> > >>> Your recent commit in ekiga broke string freeze [1]. If you have string > >>> changes to make, I suggest you branch ekiga for gnome-2-30 before > >>> committing them. > >>> > >>> Cheers, > >>> > >>> Claude > >>> > >>> [1] http://live.gnome.org/TranslationProject/HandlingStringFreezes > >> > >> I might be missing something. At > >> http://live.gnome.org/TwoPointThirtyone I see that string freeze starts > >> on July 12, isn't that right?! > > > > Yes, for the next cycle. But when a module is string freezed, it is > > forever! So the only way to 'defreeze' it is to create a branch so the > > freeze apply to the branch and no more to master. > > Is it possible to put gnome-2-26 branch in freeze, as it is the current > stable branch, and let master as unstable (we hope to create unstable > releases for it)?
Yes, of course, if you confirm that the version released in GNOME 2.30 is from the 2.26 branch, it is even the right thing to do. Claude _______________________________________________ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n