Firefox 3 Beta 1 localizations
Axel Hecht
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.
Questions?
Axel
Cédric Corazza
> In short, to get your localization into B1,
>
> * opt in.
fr locale wants to be part of this beta release. I think we meet the
requirements for this.
Thanks
Branislav Rozbora
regarding search plugins (bug 395195) waiting just for your technical
review (mic gave us r+)
Alexander L. Slovesnik
31.10.2007 02:37 you wrote:
> 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.
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.
--
Sincerely yours,
Alexander L. Slovesnik a.k.a. Unghost
==>Web-page: http://www.unghost.ru/
==>Jabber ID: a...@mozilla.ru
==>Gmail Talk ID: ung...@gmail.com
==>ICQ: 205497659
==>IRC: ircs://irc.mozilla.org:6697/mozilla-ru
Hasse
--
Hasse
sv-SE l10n team
Tomer Cohen
> * 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.
文少华
We'll make it green before Monday.
Channy Yun
Channy
> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n
>
Axel Hecht
dev-l10n mailing list
dev-...@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-l10n
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Toni Hermoso Pulido
Hash: SHA1
Please, include ca locale as well. It's already green.
En/na Axel Hecht ha escrit:
- --
Toni Hermoso Pulido
http://www.cau.cat
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHKabZ3O471rZ7Q9wRAgIPAJ9DQfBi/7ST3zP0XPXmJ414e9xsvwCgiPjZ
vUlMSoCOazLYU+6S1RLkqvw=
=4Mtj
-----END PGP SIGNATURE-----
Marek Stępień
> Hi all,
>
pl would like to be included in the beta release.
We were green until Oct 29th. So I just need to sync with the latest
en-US checkins, which I'd like to do today.
Wim
Please include fy-NL.
Translation is green for Linux and Mac.
I filed a bug on windows build
https://bugzilla.mozilla.org/show_bug.cgi?id=402027
Wim
Marcelo Poli
>
> * opt in.
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.
Damjan Georgievski
> 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?
--
damjan
Siarhei
I sync the translation today.
Tim Babych
> 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?
Guillermo López
Greeting, Guillermo <willyaranda>
Abdulkadir Topal
> 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.
--Abdulkadir
Kostas Papadimas
Kostas
Axel Hecht
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.
Axel
Axel Hecht
I created a bug to attach milestone patches again, that's
https://bugzilla.mozilla.org/show_bug.cgi?id=397506.
I expect some changes to go in after B1, yes.
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.
Axel
Gia Shervashidze
Please add "ka" to the list
We'll try to "flourish" Georgian branch of the tree for couple of days
Greetings,
g.\
Rimas Kudelis
here's your "Go!" from Lithuanian team. :)
Regards,
RQ
Axel Hecht
yesterday, string changes for the weekend.
http://blog.johnath.com/index.php/2007/11/04/sleepy-happy-wtb-5-dwarves/
and https://bugzilla.mozilla.org/show_bug.cgi?id=401575.
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.
Axel
Mad Maks
Channy Yun
> In case you didn't notice, "larry not breaking the internet" landed
> yesterday, string changes for the weekend.
>
*
*Strings may be changed without notice in the future.
So you can see changes of en-US locale change of trunk during a week.
Channy
Julen
> 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.
I don't think the Basque (eu) team could go green in a short period of
time, since our browser owner is missing for months and the browser
peer seems to be out (this weekend, at least).
Anyway, our aim is to work hard in order to get our locale into
Firefox3. Is there any approximated deadline for the last beta? It's
to have an idea of the time we have before the final string freeze.
Thank you very much,
Julen.
Ville Pohjanheimo
> In short, to get your localization into B1,
>
> * opt in.
Finnish (fi) opting in (green tboxen atm).
-ville/mozilla.fi
Pavel Franc
> Please follow up to this post, with and mention your locale.
Please include cs in the 3.0b1 release.
> * 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.
Both green for cs.
> * 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 reverted SE changes back to MOZ 1.8 branch state. The requested
changes for FF3 are attached as a patch to bug 401856 (NTH in 3.0b2)
> * Help test
> Please start testing your nightlies as much as you can. There have been
Tested.
Pavel
Czech Mozilla Team
dynamis
Please include ja/ja-JP-mac too.
And just confirmation:
We'll have only Firefox build this time and we don't need keep
Thunderbird files up-to-date now?
Is there any information about when should we ready for Thunderbird 3?
- dynamis (Manager, L10N Center)
Mozilla Japan : http://www.mozilla-japan.org/
L10N Center : http://www.mozilla-japan.org/jp/l10n/
Translation Div : http://www.mozilla-japan.org/jp/td/
Axel Hecht
> I've checked-in all files for Firefox 3 B1.
> Please include ja/ja-JP-mac too.
>
>
> And just confirmation:
> We'll have only Firefox build this time and we don't need keep
> Thunderbird files up-to-date now?
> Is there any information about when should we ready for Thunderbird 3?
>
I haven't heard more about Tb3 than David Ascher had in his blog. I'll
need to chat with him ;-)
But yes, it's only Fx these days.
Axel
Axel Hecht
Thanks for the feedback. On to your questions...
We're struggling hard to get B2 into this year, which means that B3 and
the RCs will be next year. There are not set deadlines for those, much
will depend on the initial feedback from the beta testing community,
i.e., how much work will be left.
Can Pascal or I help in any way with your first point?
Axel
amed
> In case you didn't notice, "larry not breaking the internet" landed
> yesterday, string changes for the weekend.
>
>
> http://blog.johnath.com/index.php/2007/11/04/sleepy-happy-wtb-5-dwarves/
> andhttps://bugzilla.mozilla.org/show_bug.cgi?id=401575.
>
> 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.
>
> Axel
hi Axel
Thinderbox is green for ku (Kurdish)
I hope every thing ok for ku now.
Robert Kaiser
> And just confirmation:
> We'll have only Firefox build this time and we don't need keep
> Thunderbird files up-to-date now?
> Is there any information about when should we ready for Thunderbird 3?
SeaMonkey probably has more of a plan for that release series than
Thunderbird has yet...
Robert Kaiser
Marcelo Poli
> In case you didn't notice, "larry not breaking the internet" landed
> yesterday, string changes for the weekend.
That's too bad.
So, trunk is closed?
Do we need to file a bug to update those strings?
Axel Hecht
No, the l10n tree stays open, we'll just grab a state of the tree at
some point in time for it.
The en-US tree is going through tough times of approval, of course.
Axel
Axel Hecht
we have seen an accidental string change in reporter, which, just to
make things worse, wasn't caught on tinderbox until today.
In today's Firefox meeting, we decided to add a 24 hour lag between the
go for Fx3B1 en-US. That 'go' hasn't been sent yet, and there's one
regression under investigation, so that gives you at least 24 hours to
catch up with the latest string changes.
Sorry for the confusion, the bug had an old comment saying "no string
changes", though the recent patch did in fact add one string to reporter.
There's another change from Monday, which just changed the ellipsis and
exclamation marks in the new neterror texts, you may or may not want to
copy that over.
Hope that helps, and sorry for the noise.
Axel
Axel Hecht wrote:
> 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
> 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.
>
> Questions?
>
> Axel
Axel Hecht
> Hi all,
>
> make things worse, wasn't caught on tinderbox until today.
>
> In today's Firefox meeting, we decided to add a 24 hour lag between the
> go for Fx3B1 en-US. That 'go' hasn't been sent yet, and there's one
> regression under investigation, so that gives you at least 24 hours to
> catch up with the latest string changes.
>
> Sorry for the confusion, the bug had an old comment saying "no string
> changes", though the recent patch did in fact add one string to reporter.
>
> There's another change from Monday, which just changed the ellipsis and
> exclamation marks in the new neterror texts, you may or may not want to
> copy that over.
I have just sent out mail to those localizers that regressed due to the
change on Monday.
We really want to open the en-US tree as soon as possible, so we'll pick
some optimistic timestamp for cutting the b1 relbranch.
Real localization fixes beyond that one reporter string should have
really landed by Monday, we're happy to take 'em if we get them, but we
won't push back the deadline on that.
Sorry for the mixed signals here, we're trying to balance the flock of
patches that is waiting to land post-M9 with the l10n rep, and we're
just in a deadlock of missing build tooling here. If anybody has ideas
on how to fix the problem that some localizers are trying to get the
last nightly green and others try to work towards the next, I'd be
curious. l10n-merge might help, it would just paste en-US string into
both, that would at least get us non-busted builds. Nothing ship-worthy,
but something test-worthy.
Axel
Axel Hecht
that an encoding error? Not sure.
http://l10n.mozilla.org/buildbot/linux-langpack/builds/6278/step-moz%3Acomparelocales/0
is the latest log.
Axel
Wim wrote:
> Axel,
>
> Please include fy-NL.
> Translation is green for Linux and Mac.
> I filed a bug on windows build
> https://bugzilla.mozilla.org/show_bug.cgi?id=402027
>
> Wim
>> _______________________________________________
>> dev-l10n mailing list
>> dev-...@lists.mozilla.org
>> https://lists.mozilla.org/listinfo/dev-l10n
>>
>>
>
Axel Hecht
http://l10n.mozilla.org/buildbot/linux-langpack/builds/6178/step-moz%3Acomparelocales/0
for the last log.
Axel
Marcelo Poli wrote:
> Axel Hecht escribió:
>> * opt in.
>
> 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.
Axel Hecht
http://l10n.mozilla.org/buildbot/linux-langpack/builds/6173/step-moz%3Acomparelocales/0.
Mailed Pavel earlier about this.
Axel
Axel Hecht
> Siarhei wrote:
>> Please include 'be' in beta release.
>>
>> I sync the translation today.
>
> http://l10n.mozilla.org/buildbot/linux-langpack/builds/6171/step-moz%3Acomparelocales/0
> lists the one missing reporter entity, mailed Siarhei about this already.
>
> Axel
FIXED,
http://tinderbox.mozilla.org/showlog.cgi?log=MozillaTest/1194430161.1194430775.25937.gz&fulltext=1
Axel
Axel Hecht
> Hi,
>
> We want Turkish locale (tr) to be included in beta production.
>
> Thanks,
>
> Serkan
Turkish is missing a few strings, which compare-locales.pl doesn't
catch, due to '-' in there. The buildbot pages that I point to
repeatedly show
http://l10n.mozilla.org/buildbot/linux-langpack/builds/6210/step-moz%3Acomparelocales/0
Axel
Axel Hecht
> Axel Hecht wrote:
>
> > * opt in.
> > have platform issues on the branch, please mention if those should be
> > carried over.
> 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.
> (Arabic and Farsi actually) would like the same changes.
> > For all other localizations, your judgement rules.
Hebrew is test-failed and red right now,
http://l10n.mozilla.org/buildbot/linux-langpack/builds/6186/step-moz%3Acomparelocales/0
is the latest log of compare-locales.
Axel
Axel Hecht
> Please include zh-CN also.
> We'll make it green before Monday.
This one is missing the one string in reporter,
http://l10n.mozilla.org/buildbot/linux-langpack/builds/6232/step-moz%3Acomparelocales/0
for the log
Axel
Axel Hecht
Nick Thomas
>
> I have just sent out mail to those localizers that regressed due to the
> change on Monday.
>
> We really want to open the en-US tree as soon as possible, so we'll pick
> some optimistic timestamp for cutting the b1 relbranch.
>
> Real localization fixes beyond that one reporter string should have
> really landed by Monday, we're happy to take 'em if we get them, but we
> won't push back the deadline on that.
>
> Sorry for the mixed signals here, we're trying to balance the flock of
> patches that is waiting to land post-M9 with the l10n rep, and we're
> just in a deadlock of missing build tooling here. If anybody has ideas
> on how to fix the problem that some localizers are trying to get the
> last nightly green and others try to work towards the next, I'd be
> curious. l10n-merge might help, it would just paste en-US string into
> both, that would at least get us non-busted builds. Nothing ship-worthy,
> but something test-worthy.
>
> Axel
Thanks to everyone who fixed the missing reporter string - locales which
were green before it landed are all green again.
Axel and I have agreed a cut-off time for 3.0b1 of "2007-11-07 04:11
PST". We'll be tagging shortly and building soon.
Thanks to all for their amazing work in getting up to date over the last
few days.
Cheers,
Nick Thomas (Mozilla Build)
Nick Thomas
> Thanks to everyone who fixed the missing reporter string - locales which
> were green before it landed are all green again.
>
> Axel and I have agreed a cut-off time for 3.0b1 of "2007-11-07 04:11
> PST". We'll be tagging shortly and building soon.
>
> Thanks to all for their amazing work in getting up to date over the last
> few days.
FYI, the timestamp moved to 2007/11/07 06:00 PST to get one more change.
-Nick
Axel Hecht
I have seen Piarres put in a chunk of work over the weekend to get
Basque green. I didn't see you opting in to B1 though.
Do you think that the state of the tree that we tagged and branched on
2007/11/07 06:00 PST is a good state for B1?
I currently assume that you're focused on the work instead of the
paperwork, but I want to make sure.
So far, we have treated the eu build as if you'd still opt-in, and
nothing technical has come up blocking, other than that you have an
English default bookmarks file, which we'd bite for Basque and B1. That
was https://bugzilla.mozilla.org/show_bug.cgi?id=403073.
Thanks
Axel
Axel Hecht
here is the list of localizations we're still having on our list:
be
cs (respin)
de
el
es-ES
eu (needs opt-in)
fi
fr
fy-NL
ja
ja-JP-mac
gu-IN
ka
ko
lt
pl
ru
sk (needs a search approval still)
sv-SE
tr
uk
zh-CN
We'll need testers on those, and there will be a testday tomorrow. It's
not dead-on clear which builds we'll be able to use, as there's a likely
going to be an rc3, and I don't think we actually did rc2 l10n builds.
But anyway, for a localization testing, even the rc1s should be good.
So if you could get some testers together, or participate yourself,
that'd be überhelpful. Not a word, but still.
The reason we'll be doing an RC3 is that there is a awkwardness with
migrating back and forth between fx2 and fx3 builds due to the way that
places currently imports, you'll see pointers with details on that in
the testday docs. The short story is, just use a separate profile for
testing.
Axel
Axel Hecht wrote:
> 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
> 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
