I wanted to give you a heads up notice on the fx 1.5 l10n beta plan. Not
that much heads up, but this is as far as we got.
The magic we have to pull off here is to balance the QA of the beta2
with the workload on the l10n community and the mozilla.org/com resources.
We do want to see beta for l10n builds, but we're not going to go
through too much cycles to get it, so here is the plan:
As announced on devnews [1], the mozilla repository will go through:
Oct 3: Lockdown for 1.5b2
Oct 5: Release 1.5b2
That's next Monday and Wednesday, resp.
So, for l10n, we're going to provide builds based on the beta 2
candidates, and we want you to do some serious QA on those builds. We
don't want you to spread out the current state of the tree to get some
feedback, we want you to provide Beta 2 quality builds to get polish
feedback. And no, this doesn't mean aviary.pl only ;-) .
I'll set up a wiki page to give you a chance to sign off your builds,
and you'll submit a bonsai link (I'll provide a sample) which shows the
check-ins after the build you signed off. If that link shows check-ins,
we'll not evaluate them, and we won't be doing approvals in that phase.
Once the mozilla repository (en-US) version is done, sometime wednesday,
we'll go through that wiki page, check the bonsai logs, and do release
bits for those locales that fit the criteria. If you miss this round, yo
missed it. We won't do late rounds of beta. I do expect that our
prominent locales will be participating in beta, and as much as we heart
the broad spectrum of our localizations, we can't put in a daily routine
to see if have one or two more locales to go through for a beta.
This process is pretty settled as far as we don't get any changes during
the lockdown on the en-US builds. We don't have a really good plan on
what to do when we do take changes. We may end up requiring another
round of QA on the rebuilt packages, but that QA should then be focused
on checking for changes.
I have further announcement in my queue when it comes down to trademarks
approvals. We have been revisiting some decisions on the side of en-US,
and we'll be revisiting some decisions on the l10n side. Don't expect
anything dramatic, but it would be a good idea to look at the en-US side
again and check if you search engine plugins are good, and if there
isn't stuff in your bookmarks.html that needs thought.
I'll follow up or start new threads as more clarity surfaces.
Comment away
Axel
[1]
http://developer.mozilla.org/devnews/index.php/2005/08/30/9-days-untill-15-beta
here is the page to be used for collecting the QA information about your
locales for Firefox 1.5 beta2.
http://wiki.mozilla.org/L10n:Firefox_1.5_beta_Status
Axel
And where do we grab the builds from to evaluate? I'm presuming:
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla1.8-l10n/
--
Brian King
www.mozdev.org - free project hosting for the Mozilla community
Note that the current builds in that directory are broken because of
bug 310772. They are repackaged from the 09-30 en-US builds, and with
up-to-date locale files you will see a XUL error in Options/Preferences
-> Content pane.
--
Hasse
Mozilla sv-SE L10n team
So, it seems we have nothing to sign-off at the moment.
And there have been changes in the en-US locales (region.properties)
after the three l10n teams (ga-IE, ko, nl) posted their bonsai link to
http://wiki.mozilla.org/L10n:Firefox_1.5_beta_Status ...
--
Marek Stepien <marcoos at aviary dot pl>
http://www.firefox.pl/
http://developer.mozilla.org/devnews/index.php/2005/09/06/reminder-15-beta-1-lockdown-tonight/
So Monday means 11:59pm PDT. Guys, please don't consider me as the only
piece of information to watch. I'm not going to reiterate each and every
bit, but announce the l10n-specific parts.
I do assume that you at least follow MDN, if not planet.m.o.
Axel
There have been some questions on the QA and check-in rules, so a bit
more precise:
If you do check-ins, you need to QA a build that has those changes. I
know that getting a nightly is a tricky thing, but that's the way it is.
I assume that you can gauge yourself how much of your QA work from one
windows build transfers to the next one with your changes.
Axel
i've just realized ... there is a mistake in the dummy link provided,
and consequently in all the others:
* for the toolkit directory it's written "l10" instead of "l10n"
ibon
Ibon Igartua schrieb:
--
Alexander Ihrig
------------------------------------------------------------------
Thunderbird Mail DE: http://www.thunderbird-mail.de
Enigmail DE: http://enigmail.thunderbird-mail.de/
Thanks and sorry for that. There are times when I dig wikis.
Axel
--
Sincerely yours,
Alexander L. Slovesnik a.k.a. Unghost
==>Web-page: http://forum.mozilla.ru/
==>Jabber ID: a...@mozilla.ru
==>ICQ: 205497659
==>IRC: ircs://irc.mozilla.org:6697/mozilla-ru