Re: evolution & evolution-data-server string & UI freeze break approval plea
2/2 from i18n Regards El mar, 30 mar 2021 a las 19:36, Milan Crha via gnome-i18n (< gnome-i18n@gnome.org>) escribió: > On Thu, 2021-03-18 at 15:48 +0100, Alexandre Franke wrote: > > > I'd like to ask for a string and UI freeze break approval for the > > > 3.40.1 > > > > Thanks a lot for the detailed and clear explanation. 1/2 from i18n > > for 3.40.1. > > > > Hi, > thanks Alexandre. > > May I ping here, in case someone else would give the second approval, > thus the lighter (in the translatable strings) change can get into the > gnome-40 branches, please? > > Thanks and bye, > Milan > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GNOME 40 release notes
Sure, now it's everything shown properly. Thanks El mar, 30 mar 2021 a las 22:03, Andre Klapper via gnome-i18n (< gnome-i18n@gnome.org>) escribió: > On Thu, 2021-03-25 at 08:16 +0100, Daniel Mustieles García via gnome- > i18n wrote: > > Spanish translation is complete but webpage still shows some strings > > in English. > > Not anymore. I assume things get updated once every 24 hours. > > andre > -- > Andre Klapper | ak...@gmx.net > https://blogs.gnome.org/aklapper/ > > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String freeze for GNOME 41
On Tue, Mar 30 2021 at 09:15:31 PM +0200, Alexandre Franke wrote: My opinion is that I don’t see the point of simplifying the schedule and I’m worried this will actually just increase the burden of translators. Well the thing is if we have string freeze begin at a strange time not associated with any milestone, I suspect many developers will not actually be able to remember when it begins. The status quo of the three-week freeze is just not very elegant anymore now that the .91 release is gone. Do you generally get many string change notifications? I assume they should be relatively rare, since string changes after UI freeze are not terribly common, yes? I checked just now, and I count three string change announcements for GNOME 40, all from Milan, plus one freeze break request that was mistakenly submitted during the string change announcement period because the maintainer incorrectly assumed we were in string freeze during that time. So I think changing string freeze to last five weeks probably won't make too much difference, and it will simplify our schedule such that all freezes except hard code freeze start at the same time. And of course it means more time for translators to work. Anyway, i18n team gets final say on this of course. I'll schedule it however you prefer. Michael ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GNOME 40 release notes
On Thu, 2021-03-25 at 08:16 +0100, Daniel Mustieles García via gnome- i18n wrote: > Spanish translation is complete but webpage still shows some strings > in English. Not anymore. I assume things get updated once every 24 hours. andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String freeze for GNOME 41
On Tue, Mar 30, 2021 at 8:46 PM Michael Catanzaro wrote: > Hi, > Hi, Having string freeze begin one week before 41.rc is not problematic per > se, but it is strange and makes the schedule more complicated. I don’t really see a problem with the existing schedule. > So I have two (contradictory) proposals: > > * Start string freeze with 41.rc. Disadvantage: this would reduce > string freeze from three weeks down to two. > Nope. Three weeks can already be quite short, especially considering the tension you added by inserting a “soft translation deadline” *before* the newstable release. > * Start string freeze with 41.beta and remove the string change > announcement period, increasing string freeze from three weeks to five > weeks. Disadvantage: it makes changing strings harder for developers, > and will increase the number of freeze break exception requests. > Right, and if exceptions become common occurrences, we all know how it will turn out: maintainers will miss the point and won’t just bother about the freeze anymore. > Either way would simplify the schedule, which is my goal. Any opinions > on this? > My opinion is that I don’t see the point of simplifying the schedule and I’m worried this will actually just increase the burden of translators. -- Alexandre Franke GNOME Hacker ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String freeze for GNOME 41
On Tue, Mar 30 2021 at 01:45:59 PM -0500, Michael Catanzaro wrote: With the 41.rc release moved one week earlier, if we make no changes to the timing of string freeze and string change announcement period, we would now have this: 40.beta UI freeze, string change announcement period begins (two weeks later) string freeze begins 40.rc (one week later) hard code freeze begins .0 (two weeks later) Here I meant to type 41.beta and 41.rc, oops. ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
String freeze for GNOME 41
Hi, I've posted a draft schedule for GNOME 41 development: https://wiki.gnome.org/FortyOne The most significant change is that the 41.rc release is moved one week earlier, which has implications for i18n. Previously we did this: 90 (or 40.beta) UI freeze, string change announcement period begins 91 (two weeks later) string freeze begins 92 (or 40.rc) (two weeks later) hard code freeze begins 0 (one week later) For GNOME 40, string freeze began halfway between beta and rc, at the same time it always did. This means we had two weeks of string change announcement period, then three weeks of string freeze before the final release. The string freeze was not associated with any release milestone, which was perhaps a little weird, but it was halfway between two milestones. With the 41.rc release moved one week earlier, if we make no changes to the timing of string freeze and string change announcement period, we would now have this: 40.beta UI freeze, string change announcement period begins (two weeks later) string freeze begins 40.rc (one week later) hard code freeze begins 0 (two weeks later) Having string freeze begin one week before 41.rc is not problematic per se, but it is strange and makes the schedule more complicated. So I have two (contradictory) proposals: * Start string freeze with 41.rc. Disadvantage: this would reduce string freeze from three weeks down to two. * Start string freeze with 41.beta and remove the string change announcement period, increasing string freeze from three weeks to five weeks. Disadvantage: it makes changing strings harder for developers, and will increase the number of freeze break exception requests. Either way would simplify the schedule, which is my goal. Any opinions on this? Michael ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: evolution & evolution-data-server string & UI freeze break approval plea
On Thu, 2021-03-18 at 15:48 +0100, Alexandre Franke wrote: > > I'd like to ask for a string and UI freeze break approval for the > > 3.40.1 > > Thanks a lot for the detailed and clear explanation. 1/2 from i18n > for 3.40.1. > Hi, thanks Alexandre. May I ping here, in case someone else would give the second approval, thus the lighter (in the translatable strings) change can get into the gnome-40 branches, please? Thanks and bye, Milan ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[DL]String additions to 'gnome-software.master'
This is an automatic notification from status generation scripts on: https://l10n.gnome.org. There have been following string additions to module 'gnome-software.master': + "Applications" + "In Progress" Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. https://gitlab.gnome.org/GNOME/gnome-software/commits/master ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
