String additions to 'ekiga.master'
This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'ekiga.master': + Appointment + Breakfast + Dinner + Holiday + In transit + Looking for work + Lunch + Meal + Meeting + Playing + Shopping + Sleeping + Working Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String additions to 'ekiga.master'
This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'ekiga.master': + Join a discussion group Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'ekiga.master'
On Thu, 2011-03-10 at 11:37 +, GNOME Status Pages wrote: + Join a discussion group I added missing files to POTFILES.in. andre -- mailto:ak...@gmx.net | failed http://blogs.gnome.org/aklapper | http://www.openismus.com ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'ekiga.master'
Le 08/10/2010 16:23, Andre Klapper a écrit : Hi Julien, Am Freitag, den 08.10.2010, 14:11 + schrieb GNOME Status Pages: There have been following string additions to module 'ekiga.master': + Act on the selected contact your Ekiga commit f2b0a663aa67b26c5eb0b58ff7a13b53f69c broke the string freeze. Please revert, or branch for gnome-2-32 and keep the string change only in master. Oups... sorry, I though we were out of freeze already. I reverted the string change (but not the string move in the file)... is that ok? Could you please track the gnome-2-32 branch I just created? Thanks, Snark on #gnome-hackers ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String additions to 'ekiga.master'
This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'ekiga.master': + Act on the selected contact Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'ekiga.master'
Hi Julien, Am Freitag, den 08.10.2010, 14:11 + schrieb GNOME Status Pages: There have been following string additions to module 'ekiga.master': + Act on the selected contact your Ekiga commit f2b0a663aa67b26c5eb0b58ff7a13b53f69c broke the string freeze. Please revert, or branch for gnome-2-32 and keep the string change only in master. Thanks, andre -- mailto:ak...@gmx.net | failed http://blogs.gnome.org/aklapper ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String additions to 'ekiga.master'
This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'ekiga.master': + Act on selected contact Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'ekiga.master'
Il giorno gio, 03/06/2010 alle 20.30 +0200, Eugen Dedu ha scritto: 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. 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... Just a little OT: this misunderstanding of release time and versions could be a good example for new moduleset proposal. :) ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'ekiga.master'
On 03/06/10 20:43, Andre Klapper wrote: Am Donnerstag, den 03.06.2010, 20:30 +0200 schrieb Eugen Dedu: 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 was already released two months ago. According to http://ftp.gnome.org/pub/GNOME/desktop/2.30/2.30.0/sources/ Ekiga 3.2.6 was used. The GNOME schedule can be found at http://live.gnome.org/TwoPointThirtyone/ . 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. Exactly. 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... You did not branch Ekiga yet after GNOME 2.30 was released. And all the branches of those apps used for GNOME 2.30 are string frozen for all times and one day. So branch Ekiga for gnome-2-30, gnome-2-30 will be used for more stable releases of Ekiga in GNOME 2.30, and feel free to changes any strings in git master which will be branched to gnome-3-0 in a few months. Or so. To resume: if I make a branch called gnome-2-30 from current stable branch (gnome-2-26), it will automatically become current stable branch and will be string frozen forever, while master becomes ok for string changes until 1-2 months before gnome 3.0, cf. its roadmap. Is all that right? -- Eugen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'ekiga.master'
Le vendredi 04 juin 2010 à 10:08 +0200, Eugen Dedu a écrit : On 03/06/10 20:43, Andre Klapper wrote: Am Donnerstag, den 03.06.2010, 20:30 +0200 schrieb Eugen Dedu: 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 was already released two months ago. According to http://ftp.gnome.org/pub/GNOME/desktop/2.30/2.30.0/sources/ Ekiga 3.2.6 was used. The GNOME schedule can be found at http://live.gnome.org/TwoPointThirtyone/ . 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. Exactly. 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... You did not branch Ekiga yet after GNOME 2.30 was released. And all the branches of those apps used for GNOME 2.30 are string frozen for all times and one day. So branch Ekiga for gnome-2-30, gnome-2-30 will be used for more stable releases of Ekiga in GNOME 2.30, and feel free to changes any strings in git master which will be branched to gnome-3-0 in a few months. Or so. To resume: if I make a branch called gnome-2-30 from current stable branch (gnome-2-26), it will automatically become current stable branch and will be string frozen forever, while master becomes ok for string changes until 1-2 months before gnome 3.0, cf. its roadmap. Is all that right? The reasoning is right, but as you told us that GNOME 2.30 shipped ekiga from the stable gnome-2-26 branch, you do not have to create yet another gnome-2-30 stable branch. I just fixed l10n.gnome.org to consider gnome-2-26 as the branch used for GNOME 2.30. So you can now freely make string changes in master. In the future, please inform gnome-i18n and fix JHBuild moduleset [1] to reflect using a stable branch for a specific GNOME release. Claude [1] http://git.gnome.org/browse/jhbuild/tree/modulesets/gnome-suites-2.30.modules ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'ekiga.master'
On 02/06/10 22:02, Claude Paroz wrote: Le mercredi 02 juin 2010 à 17:39 +, 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?! -- Eugen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'ekiga.master'
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 +, 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
String additions to 'ekiga.master'
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:DSL, 3: LAN, 4: Custom + Kind of network selected in the druid Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'ekiga.master'
Am Donnerstag, den 03.06.2010, 18:24 + schrieb GNOME Status Pages: There have been following string additions to module 'ekiga.master': + 0: 56Kbps, 1: ISDN, 2:DSL, 3: LAN, 4: Custom + Kind of network selected in the druid This is just the revert to the previous string. andre -- mailto:ak...@gmx.net | failed http://www.iomc.de/ | http://blogs.gnome.org/aklapper ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'ekiga.master'
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 +, 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. 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. -- Eugen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'ekiga.master'
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 +, 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 gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String additions to 'ekiga.master'
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. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'ekiga.master'
Le mercredi 02 juin 2010 à 17:39 +, 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 ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'ekiga.master'
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 +, 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. Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
