We need to figure out which locales to ship in Beta 5, and on which platforms. We need to pass over a date for tagging/build, too.

This was in build-config for B4, let's move it over. I was torn myself.

Here's the status of l10n, according to http://l10n.mozilla.org/dashboard/Firefox3/Beta5/, and the blocker bugs for this bug. Comments: I'd like to take an optimistic approach for "cs" and "ku". Both are green on the relevant boxes, but didn't opt-in for B5. They did opt-in to previous releases, though we didn't ship "ku" so far. The idea for those two is to create builds (and updates for "cs"), and to only put them up when we get a opt-in. We could take the really optimistic path and put them up, and be ready to pull them if they complain, but I'd rather stick to our opt-in path for now. I'm adding Serbian, accepting a bunch of untranslated strings and other problems shown in the dependent bug. We haven't had Serbian even on 2.0, so getting some testing on this should be good, even if we have a good deal of known problems. The localizer knows about those, and is not intending to ship it like this for real, so this is really just a beta thing. I removed windows due to the installer really not being usable, if you don't know what the buttons mean. I also removed the RTL locales on mac. Comments? PS: Not assigning this to me, as I'm not readily available over the weekend. Suggested l10n pull date is 4am PST, March 20th. Tinderbox status cron job was stopped to reflect that. buildbot status kept locally for now. Unless we land bustage fixes later.

we have hear from Kurdish and they are officially opted in now. IMHO we go ahead with cs copying chofmann and gavin for help given pike is away on technical side, I can take lead and help in any way needed

any word from ga-IE? they also went out in previous releases, but have been yanked in axel's patch.

ga-IE heard from kevin, he is on vacation and couldn't make this beta so we go ahead without him unfortunately en-ZA should be there as well, understand they have en-US web service defaults but that is ok for this beta as they are not likely to change services for RC1 and services are relevant to their user base

Comment on attachment 310744 [details] [diff] [review] update shipped-locale for Beta 5, take 1 r=chofmann,mic we confirmed the list matches up with axel's comments and should be ready to go. we might want to add en-ZA to beta5, but lets make sure we get all the tinderbox stuff set up first to we make sure it doesn't interupt the cycle for the rest of the locales. gavin/reed/other... this is ready for check-in

en-ZA doesn't even build yet, and I see no point in releasing en-ZA with en-US web services. The impact from a language point of view should be really minor, as is the actual localization work. Before we check this in, any comments on RTL and Mac? And I'd like to get confirmation from joduinn or beltzner on tentatively landing cs.

Say nothing ever changes with RTL and Mac: are we going to strand the people currently using 2.0.0.x (which I remember looking like ass around the search bar, though I don't know whether or by how much Fx3 is worse) on whatever winds up being end-of-life? (Have we already done that with Thunderbird, where we shipped 1.5.0.x and haven't shipped 2.x?)

As per discussion in the serbian bug, the windows installer was apparently an issue with chofmann and I missing fonts, this shouldn't be a problem for people interested in a serbian localization. New patch removing the platformishness of Serbian.

Comment on attachment 310866 [details] [diff] [review] actually ship serbian on windows, too. I would prefer beltzner to review this patch, like we've done in previous releases... I dont have enough context to make informed decision here.

re comment #7, i didn't know en-ZA doesn't build yet. i do believe that releasing with en-US defaults is still relevant (as Afrikaans users are also english speakers) and they want feedback on their build translation, etc. I have been tracking suggestions to web services in bug 418302. all that to say, can we ship them? (I understand we may have missed time window as well) or is the build technically very poor?

> re comment #7, i didn't know en-ZA doesn't build yet. I'm guessing it does build; but I think it's still in the incubator, and not set up in tinderbox. -> https://bugzilla.mozilla.org/show_bug.cgi?id=424210 I think there is just more work to get things set up before its ready to be released. any how lets not wait for it.

There is no en-ZA tinderbox at all. That stuff never ever ran through a single build cycle on our side. I have no idea why en-ZA matters to Afrikaans people either, as we're having an Afrikaans build, shipping with this beta. Read "af". en-ZA is English (South Africa), and I yet have to understand where the value of that build is compared to en-GB or en-US, as long as it's shipping with en-US defaults and community hooks.

my apologies to all, i had af and en-ZA confused, d'oh :( we can debate value of en-ZA in other places ;)

Comment on attachment 310866 [details] [diff] [review] actually ship serbian on windows, too. r+a1.9b5=beltzner

FIXED. Unhooked the Serbian bug, per previous discussion. Checking in shipped-locales; /cvsroot/mozilla/browser/locales/shipped-locales,v <-- shipped-locales new revision: 1.8; previous revision: 1.7 Pull date for l10n is 4am PST, March 20th.