I see that a bunch of teams try to keep the trunk up-to-date.
We're currently trying to ramp down on Firefox 3 B1, which is going into code freeze by the end of the week. We expect to see only a few more string changes until then, you can follow the triage bug queries for M9 blockers on http://wiki.mozilla.org/Firefox3/StatusMeetings/2007-10-30 for up-to-date information.
We intend to do localized builds on a best-effort basis for B1. That is, whoever is ready, and says so, will get shipped.
Build date is Monday morning, that is, you'll have the weekend to catch up with anything landing late, and you should have a pretty quiet time in the tree this week. We're not approving any "free lunches" anymore, only real B1 blockers go in. The amount of bugs landing should be down to 1 or 2 by Wednesday night, code freeze for /cvsroot is intended to be on Thursday.
If you find anything that blocks us from releasing any localizations at all, please make sure that bugs are filed on it, and put me on CC.
We're not going to block B1 on any particular locale, though.
In short, to get your localization into B1,
* opt in. Please follow up to this post, with and mention your locale. If you have platform issues on the branch, please mention if those should be carried over. This is really to cover for folks that kept the tree green, but that don't feel like their localization should really be Firefox 3 Beta 1. I'd make a special rule for Hebrew here, for which wide RTL testing is gonna be essential, and we apparently have bugs here. For all other localizations, your judgement rules. We're not having a set deadline for this, but the earlier you have a good judgement the better. Build is going to try to build all localizations, but this is mostly a matter of convenience. It does give us some flexibility, though.
* go green. We're going to run some form of the compare locales tests, so you should pass those. Passing tinderbox on mozilla-l10n-ab-CD might not suffice, have an eye on linux-langpack 1slave and 2 on http://tinderbox.mozilla.org/showbuilds.cgi?tree=MozillaTest, too. I'll probably beef up that test tomorrow, at which point the python compare-locales will have yet more test coverage than the perl version on mozilla-l10n-.. already. This needs to happen by Monday early morning PST.
* Don't mess with search etc. Please make sure that search and bookmarks etc are compatible with what we do for Fx2, unless otherwise tracked in bugzilla, reviewed and approved.
* Help test Please start testing your nightlies as much as you can. There have been some builds around that just don't start up. I blame bad timing for most of them, but some might just have bugs. In particular when we have RCs next week, any pounding of those builds in particular will be welcome. QA will do spot testings as time and resources permit.
Overall, we're trying to keep this as low key as possible right now, without embarrassing localizers or Mozilla without good reason.
Being part of B1 does not affect your likelyhood to ship in Fx3 in the initial release, too.
Hi Axel, sk locale is also ready for b1. We have one opened bug regarding search plugins (bug 395195) waiting just for your technical review (mic gave us r+)
> * opt in. > Please follow up to this post, with and mention your locale. If you > have platform issues on the branch, please mention if those should be > carried over.
Hi, Pike. Russian locale wants to be part of 3.0b1 release.
> * Don't mess with search etc. > Please make sure that search and bookmarks etc are compatible with what > we do for Fx2, unless otherwise tracked in bugzilla, reviewed and approved.
I just have synced trunk searchplugins with 1.8.1 searchplugins. I think we meet the requirements for Firefox 3.0b1 release.
> * opt in. > Please follow up to this post, with and mention your locale. If you > have platform issues on the branch, please mention if those should be > carried over. We are almost ready. tinderbox is green (currently orange, but I'll make it green tomorrow), and we have few more string changes I would like to commit before freeze (but none are blockers). he-IL, tested in Linux and Windows. We don't have OSX tester yet but hope to get one soon. > This is really to cover for folks that kept the tree green, but that > don't feel like their localization should really be Firefox 3 Beta 1. > I'd make a special rule for Hebrew here, for which wide RTL testing is > gonna be essential, and we apparently have bugs here. Well, we have few theme issues, but I guess that other RTL locales (Arabic and Farsi actually) would like the same changes. > For all other localizations, your judgement rules.
> I see that a bunch of teams try to keep the trunk up-to-date.
> We're currently trying to ramp down on Firefox 3 B1, which is going into > code freeze by the end of the week. We expect to see only a few more > string changes until then, you can follow the triage bug queries for M9 > blockers on http://wiki.mozilla.org/Firefox3/StatusMeetings/2007-10-30 > for up-to-date information.
> We intend to do localized builds on a best-effort basis for B1. That is, > whoever is ready, and says so, will get shipped.
> Build date is Monday morning, that is, you'll have the weekend to catch > up with anything landing late, and you should have a pretty quiet time > in the tree this week. We're not approving any "free lunches" anymore, > only real B1 blockers go in. The amount of bugs landing should be down > to 1 or 2 by Wednesday night, code freeze for /cvsroot is intended to be > on Thursday.
> If you find anything that blocks us from releasing any localizations at > all, please make sure that bugs are filed on it, and put me on CC.
> We're not going to block B1 on any particular locale, though.
> In short, to get your localization into B1,
> * opt in. > Please follow up to this post, with and mention your locale. If you > have platform issues on the branch, please mention if those should be > carried over. > This is really to cover for folks that kept the tree green, but that > don't feel like their localization should really be Firefox 3 Beta 1. > I'd make a special rule for Hebrew here, for which wide RTL testing is > gonna be essential, and we apparently have bugs here. > For all other localizations, your judgement rules. > We're not having a set deadline for this, but the earlier you have a > good judgement the better. Build is going to try to build all > localizations, but this is mostly a matter of convenience. It does give > us some flexibility, though.
> * go green. > We're going to run some form of the compare locales tests, so you > should pass those. Passing tinderbox on mozilla-l10n-ab-CD might not > suffice, have an eye on linux-langpack 1slave and 2 on > http://tinderbox.mozilla.org/showbuilds.cgi?tree=MozillaTest, too. I'll > probably beef up that test tomorrow, at which point the python > compare-locales will have yet more test coverage than the perl version > on mozilla-l10n-.. already. > This needs to happen by Monday early morning PST.
> * Don't mess with search etc. > Please make sure that search and bookmarks etc are compatible with > what we do for Fx2, unless otherwise tracked in bugzilla, reviewed and > approved.
> * Help test > Please start testing your nightlies as much as you can. There have > been some builds around that just don't start up. I blame bad timing for > most of them, but some might just have bugs. In particular when we have > RCs next week, any pounding of those builds in particular will be > welcome. QA will do spot testings as time and resources permit.
> Overall, we're trying to keep this as low key as possible right now, > without embarrassing localizers or Mozilla without good reason.
> Being part of B1 does not affect your likelyhood to ship in Fx3 in the > initial release, too.
----- Original Message ---- From: Axel Hecht <l...@mozilla.com> To: dev-l...@lists.mozilla.org Sent: Wednesday, October 31, 2007 5:07:58 AM Subject: Firefox 3 Beta 1 localizations
Hi all,
I see that a bunch of teams try to keep the trunk up-to-date.
We're currently trying to ramp down on Firefox 3 B1, which is going into code freeze by the end of the week. We expect to see only a few more string changes until then, you can follow the triage bug queries for M9
We intend to do localized builds on a best-effort basis for B1. That is, whoever is ready, and says so, will get shipped.
Build date is Monday morning, that is, you'll have the weekend to catch
up with anything landing late, and you should have a pretty quiet time in the tree this week. We're not approving any "free lunches" anymore, only real B1 blockers go in. The amount of bugs landing should be down to 1 or 2 by Wednesday night, code freeze for /cvsroot is intended to be on Thursday.
If you find anything that blocks us from releasing any localizations at
all, please make sure that bugs are filed on it, and put me on CC.
We're not going to block B1 on any particular locale, though.
In short, to get your localization into B1,
* opt in. Please follow up to this post, with and mention your locale. If you have platform issues on the branch, please mention if those should be carried over. This is really to cover for folks that kept the tree green, but that don't feel like their localization should really be Firefox 3 Beta 1. I'd make a special rule for Hebrew here, for which wide RTL testing is gonna be essential, and we apparently have bugs here. For all other localizations, your judgement rules. We're not having a set deadline for this, but the earlier you have a good judgement the better. Build is going to try to build all localizations, but this is mostly a matter of convenience. It does give
us some flexibility, though.
* go green. We're going to run some form of the compare locales tests, so you should pass those. Passing tinderbox on mozilla-l10n-ab-CD might not suffice, have an eye on linux-langpack 1slave and 2 on http://tinderbox.mozilla.org/showbuilds.cgi?tree=MozillaTest, too. I'll
probably beef up that test tomorrow, at which point the python compare-locales will have yet more test coverage than the perl version on mozilla-l10n-.. already. This needs to happen by Monday early morning PST.
* Don't mess with search etc. Please make sure that search and bookmarks etc are compatible with what we do for Fx2, unless otherwise tracked in bugzilla, reviewed and approved.
* Help test Please start testing your nightlies as much as you can. There have been some builds around that just don't start up. I blame bad timing for most of them, but some might just have bugs. In particular when we have
RCs next week, any pounding of those builds in particular will be welcome. QA will do spot testings as time and resources permit.
Overall, we're trying to keep this as low key as possible right now, without embarrassing localizers or Mozilla without good reason.
Being part of B1 does not affect your likelyhood to ship in Fx3 in the initial release, too.
> I see that a bunch of teams try to keep the trunk up-to-date.
> We're currently trying to ramp down on Firefox 3 B1, which is going into > code freeze by the end of the week. We expect to see only a few more > string changes until then, you can follow the triage bug queries for M9 > blockers on http://wiki.mozilla.org/Firefox3/StatusMeetings/2007-10-30 > for up-to-date information.
> We intend to do localized builds on a best-effort basis for B1. That is, > whoever is ready, and says so, will get shipped.
> Build date is Monday morning, that is, you'll have the weekend to catch > up with anything landing late, and you should have a pretty quiet time > in the tree this week. We're not approving any "free lunches" anymore, > only real B1 blockers go in. The amount of bugs landing should be down > to 1 or 2 by Wednesday night, code freeze for /cvsroot is intended to be > on Thursday.
> If you find anything that blocks us from releasing any localizations at > all, please make sure that bugs are filed on it, and put me on CC.
> We're not going to block B1 on any particular locale, though.
> In short, to get your localization into B1,
> * opt in. > Please follow up to this post, with and mention your locale. If you > have platform issues on the branch, please mention if those should be > carried over. > This is really to cover for folks that kept the tree green, but that > don't feel like their localization should really be Firefox 3 Beta 1. > I'd make a special rule for Hebrew here, for which wide RTL testing is > gonna be essential, and we apparently have bugs here. > For all other localizations, your judgement rules. > We're not having a set deadline for this, but the earlier you have a > good judgement the better. Build is going to try to build all > localizations, but this is mostly a matter of convenience. It does give > us some flexibility, though.
> * go green. > We're going to run some form of the compare locales tests, so you > should pass those. Passing tinderbox on mozilla-l10n-ab-CD might not > suffice, have an eye on linux-langpack 1slave and 2 on > http://tinderbox.mozilla.org/showbuilds.cgi?tree=MozillaTest, too. I'll > probably beef up that test tomorrow, at which point the python > compare-locales will have yet more test coverage than the perl version > on mozilla-l10n-.. already. > This needs to happen by Monday early morning PST.
> * Don't mess with search etc. > Please make sure that search and bookmarks etc are compatible with > what we do for Fx2, unless otherwise tracked in bugzilla, reviewed and > approved.
> * Help test > Please start testing your nightlies as much as you can. There have > been some builds around that just don't start up. I blame bad timing for > most of them, but some might just have bugs. In particular when we have > RCs next week, any pounding of those builds in particular will be > welcome. QA will do spot testings as time and resources permit.
> Overall, we're trying to keep this as low key as possible right now, > without embarrassing localizers or Mozilla without good reason.
> Being part of B1 does not affect your likelyhood to ship in Fx3 in the > initial release, too.
> I see that a bunch of teams try to keep the trunk up-to-date.
> We're currently trying to ramp down on Firefox 3 B1, which is going into > code freeze by the end of the week. We expect to see only a few more > string changes until then, you can follow the triage bug queries for M9 > blockers on http://wiki.mozilla.org/Firefox3/StatusMeetings/2007-10-30 > for up-to-date information.
> We intend to do localized builds on a best-effort basis for B1. That is, > whoever is ready, and says so, will get shipped.
> Build date is Monday morning, that is, you'll have the weekend to catch > up with anything landing late, and you should have a pretty quiet time > in the tree this week. We're not approving any "free lunches" anymore, > only real B1 blockers go in. The amount of bugs landing should be down > to 1 or 2 by Wednesday night, code freeze for /cvsroot is intended to be > on Thursday.
> If you find anything that blocks us from releasing any localizations at > all, please make sure that bugs are filed on it, and put me on CC.
> We're not going to block B1 on any particular locale, though.
> In short, to get your localization into B1,
> * opt in. > Please follow up to this post, with and mention your locale. If you > have platform issues on the branch, please mention if those should be > carried over. > This is really to cover for folks that kept the tree green, but that > don't feel like their localization should really be Firefox 3 Beta 1. > I'd make a special rule for Hebrew here, for which wide RTL testing is > gonna be essential, and we apparently have bugs here. > For all other localizations, your judgement rules. > We're not having a set deadline for this, but the earlier you have a > good judgement the better. Build is going to try to build all > localizations, but this is mostly a matter of convenience. It does give > us some flexibility, though.
> * go green. > We're going to run some form of the compare locales tests, so you > should pass those. Passing tinderbox on mozilla-l10n-ab-CD might not > suffice, have an eye on linux-langpack 1slave and 2 on > http://tinderbox.mozilla.org/showbuilds.cgi?tree=MozillaTest, too. I'll > probably beef up that test tomorrow, at which point the python > compare-locales will have yet more test coverage than the perl version > on mozilla-l10n-.. already. > This needs to happen by Monday early morning PST.
> * Don't mess with search etc. > Please make sure that search and bookmarks etc are compatible with > what we do for Fx2, unless otherwise tracked in bugzilla, reviewed and > approved.
> * Help test > Please start testing your nightlies as much as you can. There have > been some builds around that just don't start up. I blame bad timing for > most of them, but some might just have bugs. In particular when we have > RCs next week, any pounding of those builds in particular will be > welcome. QA will do spot testings as time and resources permit.
> Overall, we're trying to keep this as low key as possible right now, > without embarrassing localizers or Mozilla without good reason.
> Being part of B1 does not affect your likelyhood to ship in Fx3 in the > initial release, too.
es-AR is almost ready. Linux and Mac are green. Windows have one or two files with wrong enconding. My editors use \u encoding in all properties files and I must change it in the installer properties files.
On 31 , 01:37, Axel Hecht <l...@mozilla.com> wrote:
> In short, to get your localization into B1,
> * opt in.
Hello Axel. Please include Ukrainian in the Beta 1.
> * Don't mess with search etc. > Please make sure that search and bookmarks etc are compatible with > what we do for Fx2, unless otherwise tracked in bugzilla, reviewed and > approved.
Currently search engines etc. are as they were in branch. I have few ideas on improving feed readers but will commit new ones only after proper approval and discussion in Bugzilla.
> * Help test
I am, personally, using Trunk on Linux and Windows. Hoping to get Mac tester soon.
> Being part of B1 does not affect your likelyhood to ship in Fx3 in the > initial release, too.
While we are on it, can you remind what things affect that likelyhood?
> Hi all, > * opt in. > Please follow up to this post, with and mention your locale. If you > have platform issues on the branch, please mention if those should be > carried over.
We'll try to meet this release, please add "de" to the list.
Tim Babych wrote: > On 31 , 01:37, Axel Hecht <l...@mozilla.com> wrote: >> In short, to get your localization into B1,
>> * opt in.
> Hello Axel. > Please include Ukrainian in the Beta 1.
>> * Don't mess with search etc. >> Please make sure that search and bookmarks etc are compatible with >> what we do for Fx2, unless otherwise tracked in bugzilla, reviewed and >> approved.
> Currently search engines etc. are as they were in branch. > I have few ideas on improving feed readers but will commit new ones > only after proper approval and discussion in Bugzilla.
>> * Help test
> I am, personally, using Trunk on Linux and Windows. Hoping to get Mac > tester soon.
>> Being part of B1 does not affect your likelyhood to ship in Fx3 in the >> initial release, too.
> While we are on it, can you remind what things affect that likelyhood?
I expect to see a combination of localization completeness, QA - both community testings and moco, website stuff, and possibly some level of SUMO status. Plus the regular search/region.properties stuff. That should be easier this time around as we're only having a limited amount of changes in the infrastructure. How much web-application hooks will cause work is still subject of discussion.
Damjan Georgievski wrote: >> We're currently trying to ramp down on Firefox 3 B1, which is going into >> code freeze by the end of the week. > ... >> Questions?
> Can someone share how much work is it to update the 1_8_BRANCH l10n to > trunk? I mean translation work.
> Also Axel, how about after Beta1 ... is it expected to have a lot of string > changes after B1?
We're expecting to have 3 betas, and string freeze will not be before 2 weeks before the last beta. We will continuously see less changes until then, at least that's the plan, which, read the other way around, means more changes after B1.
Note that we're doing a whole lot of new things, including places, larry, EV certs and SSL errors etc, which will get much more feedback in B1 and beyond, and we'll react on that feedback, in one way or the other. Which in large parts means that we're trying our best in that UI, but if it doesn't work, we'll change it, and we'll know how once we get there.
I see that some of you are catching up, that's cool.
Given that, I don't expect changes to the timeline coming up even though development landed string changes on Saturday. Unless development still has open blockers, build is going to kick off the builds on Monday morning.
This is unfortunate for us all, but it's the compromise that should be right in the big picture. Pushing beta is a bad option, as is breaking the internet (as Jonathan puts it).
Sorry to everybody that tried and won't be able to catch up with the landing.
For those that get the change in, thanks a lot for that.
