late-10n bug list winding down for Firefox 2.
Chris Hofmann
There are only 8 remaining bugs and many of these will be fixed in the
next couple of days.
I hope to have an update next week with some projections on when all the
late-l10n bug list will hit zero, some guidance on how to approach some
of the final late-l10n work, and some target dates for when localization
packages will need to be completed, tested, and signed off to ship
simultaneously on the Firefox release date.
To help make sure everything is moving along ok be sure to file blocking
bugs, start discussions on this list, or if you need other help r see
blocking issues that you would like to discuss privately send mail to
Axel and I.
Axel and I will also be setting up l10n conference calls/IRC sessions
late next week for Q and A, and as a forum to raise issues that might be
affecting individual or all localization work for Firefox 2. Date,
time, and call in numbers to follow in the next couple of days. Like
calls in the past we will do one session for Euro timezones and one for
Asia.
It looks like things are shaping up to ship a lot of locales
simultaneously when Firefox 2 goes out the door.
Thanks
Chris Hofmann
Axel Hecht
To follow up on this, we're not frozen for Firefox 2 Beta 2 so far, and
we won't be until it says so on http://developer.mozilla.org/devnews/.
The reason for that is that we have a few late-l10n bugs left, and that
count is supposed to get down to 0, excluding help, for b2 codefreeze.
3 of the remaining 7 bugs in Chris' query are help bugs, and the rest
are pretty smallish. I had to adjust one bug, though, +1.
https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=nowords&keywords=fixed1.8.1+verified1.8.1&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-firefox2%2B&field0-0-1=flagtypes.name&type0-0-1=equals&value0-0-1=blocking1.8.1%2B&field0-1-0=target_milestone&type0-1-0=equals&value0-1-0=Firefox+2+beta2&field0-1-1=target_milestone&type0-1-1=equals&value0-1-1=mozilla1.8.1beta2&field0-2-0=keywords&type0-2-0=substring&value0-2-0=late-l10n
is the query I used, which automagically excludes the help bugs, which
is good news, as it tells us that the triage meetings are on track with
late-l10n and b2 freeze.
If we find new bugs that would impact l10n and absolutely must be fixed,
we'll need to make painful decisions of course, and it will largely
depend on the nature of the bug and the timing which evil we pick.
Axel
Hasse
wrote...
> If we find new bugs that would impact l10n and absolutely must be fixed,
> we'll need to make painful decisions of course, and it will largely
> depend on the nature of the bug and the timing which evil we pick.
I see that work is being done to generate localized URLs outside of
l10n files. Are you also going to do that with the "how Firefox
protects you" link in the phishing warning bubble?
> http://lxr.mozilla.org/mozilla1.8/source/browser/locales/en-US/chrome/browser/safebrowsing/phishing-afterload-warning-message.dtd#9
--
Hasse
sv-SE l10n team
Axel Hecht
Thanks for asking. We'll see, that'd be bug 344144.
Axel