Looking at http://people.mozilla.com/~axel/status-1.8/ and http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla1.8-l10n-ro, the Romanian localization is behind. Note that bug 344132 reports help to be broken, too. Not setting a target milestone for this, I'd like to get some feedback on the timing from the l10n team.
any updates on status for ro?
Whiteboard: tinderbox red
Moving over to 188.8.131.52
Iulian, do you have news for us on the Romanian locale for Firefox 2.0.0.x?
Moving out one release, are there any news on the Romanian team-building?
Translation of the interface is done, the help is 70% untranslated (in progress), installer strings need to be revised (todo). Is there a date for the next firefox update release? What's left of the translation would take roughly a week.
Alexandru, we're in the final stages of 184.108.40.206, and the next release after that would be some 6-8 weeks after that. I'd suggest to try to start landing stuff soon after 220.127.116.11 opens, by attaching patches to bugs (bug 361482 is a good candidate) and to request approval18.104.22.168 on those.
Axel, could you explain please „attaching patches”? There are a lot of files modified since the cvs checkout, how do I deliver them? Create an archive with all of them or make patch files for all of them ? I don't have CVS write account yet.
Alexandru, seems like we're ready to get Romanian into beta? That'd be for .4, and with some wider testing we'd go for an all-official release for .5? The only difference between beta and not is that beta localizations don't show up on all.html, otherwise the builds are the same thing.
Yes, please go ahead with beta.
Created attachment 262761 [details] [diff] [review] add Romanian to browser/locales/shipped-locales Tim, can I get a QA OK on adding Romanian to the beta localizations for Firefox 22.214.171.124?
Assignee: iulianu → l10n
Status: NEW → ASSIGNED
Attachment #262761 - Flags: review?(timr)
Comment on attachment 262761 [details] [diff] [review] add Romanian to browser/locales/shipped-locales Asking for approval for adding Romanian as beta localization for 126.96.36.199
Attachment #262761 - Flags: approval188.8.131.52?
Comment on attachment 262761 [details] [diff] [review] add Romanian to browser/locales/shipped-locales approved for 184.108.40.206, a=dveditz for release-drivers
Attachment #262761 - Flags: approval220.127.116.11? → approval18.104.22.168+
Checked in on the branch, adding fixed22.214.171.124 keyword, though leaving open for getting Romanian out of beta. YEEHAW, and congratulations everyone, shipping Romanian beta for 126.96.36.199.
What exactly means getting Romanian out of beta?
We'll need some level of testing, unfortunately, we're still working a bit on formalizing that. Key components will be: - a set of users using the beta builds for their daily browsing. The more, the merrier. Try to get some information from your testers, in particular, which platforms they're on. I'll ask you to report on the feedback your testers had, and how many bugs they found (and which of those got fixed). - a set of test runs on all three platforms (win, mac, linux). If you don't have access to a particular platform, please let us know. The set of tests should be covered in litmus, litmus.mozilla.org. This point is somewhat fuzzy, but should clear up next week or two. I'll let you know. Does that answer your question?
So I'm waiting for formalizing, which of I'll be notified here?
First of all, you'll be waiting for builds ;-). Those will show up in the release notes for Firefox 188.8.131.52. That will have the right URLs to use for download, as those will trigger our download statistics, which is yet another valuable datapoint. Once we have builds, you can immediately ring all bells and whistles for getting your beta testing community on those builds, and to pound them hard and often. Only the platform tests and whatever else coverage we'll figure out to have on litmus will need to wait on us, and yes, I'll post here with what we come up with, and in the l10n newsgroup.
Hi Axel, We're in beta mode for quite some time, anything new about what and where needs to be done to get out of this mode? Also, do you think we should start updating translations on head for firefox3, or we should wait for a signal like strings frozen ?
Hi Axel, Can we close this and go on with Firefox 3? If you could please tell me if there's a new branch for Firefox 3 to which I should commit, or just put it in HEAD ?
Yes, this is FIXED. Thanks a lot. And yes, next up is Firefox 3, and HEAD is open for work there. There is improved testing tooling there, too, http://l10n.mozilla.org/buildbot/waterfall is running on trunk, and reporting to http://tinderbox.mozilla.org/showbuilds.cgi?tree=MozillaTest, too. More goodness is in the pipeline.
Status: ASSIGNED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.