Le jeudi 03 juin 2010 à 20:30 +0200, Eugen Dedu a écrit : > On 03/06/10 16:30, Claude Paroz wrote: > > 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. > > We do not yet know which version will be released with gnome 2.30. So I > reverted the change, sorry for bothering you.
GNOME 2.30 is already out. Looking at http://ftp.gnome.org/pub/GNOME/desktop/2.30/2.30.0/sources/ the ekiga version is 3.2.6. Can you tell us if this is from the gnome-2-26 branch or from master ? > I still do not understand why this constrain. It seems to me that the > natural solution is that 1-2 months before each release, the branch (or > the HEAD if the branch does not exist) enters string freeze, and before > that everything is allowed. This gives translators 1-2 months to work > on translations. But we are now four months away from the release and > we cannot make string changes for this release... > > Reference: "The string freeze will continue for every module affected by > the freeze until the module has branched for gnome-2-30. Only after that > point, HEAD will no longer be affected by the string freeze. The > gnome-2-30 branch will be affected by the string freeze in eternity." If you have to make string changes in a (string-)freezed stable branch, probably for bug fixing, it is always possible to ask gnome-i18n for an exception. If you only want to continue normal development on master, the explanation seems clear: branch, branch, branch :-) Then you are free to do whatever you want on master. Feel free to come and ask on #i18n for any further information. Claude _______________________________________________ gnome-i18n mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-i18n
