This is a tracker bug for releasing Firefox km. This is based on the registration bug 551886. This bug is not that detailed, but as we get particular work items, they should block this bug for tracking and discoverability. The "bugs" here are tracking indiviual items of work. Some of those will depend on the localization team to be driven to completion, others are for infrastructure that will be handled by staff. I'll indicate which in the individual bugs.
The dashboard is now up, at https://l10n-stage-sj.mozilla.org/shipping/dashboard?locale=km. I hope to get builds RSN, too. There are only a few things to fix, see https://l10n-stage-sj.mozilla.org/dashboard/compare?run=181727 for starters. If you need help with that, drop a note. Also, now that we've got a repo up, you, Vannak, and Arky should set up a plan on who's going to push to the repos.
I have fixed it already. ;)
Hi, just a quick update. We're still waiting for the actual builds, coop said he landed those today, so tomorrow we should get builds. Sadly, the setup of our infrastructure took longer than usual, and we're not all set up, and Firefox 10 moved to Beta earlier today. To give us a proper timing, and to make things less complicated technically, we'll want to move your work onto the Firefox 11 train. One thing that came in with 11 is another rename of two files. If we can help with those, please follow up here. Beyond that, we're hoping to see you get into good shape to land and test really soon now. Thanks. Axel
:pike (In reply to Axel Hecht [:Pike] from comment #3) > Hi, just a quick update. > > We're still waiting for the actual builds, coop said he landed those today, > so tomorrow we should get builds. We're getting Khmer Aurora builds now, so thats good. > One thing that came in with 11 is another rename of two files. If we can > help with those, please follow up here. What are the names of the two files? If this is in a separate bug, just point us to bug#. > Thanks. Axel This bug is "Firefox release tracker", but what about Thunderbird Khmer? The strings are now 100% localised in narro. Should we morph this tracking bug, or would you prefer we file a separate "Thunderbird release tracker" bug?
Depends on: 725049
km should be going green on the dashboard as hg for aurora and beta are now matching. The dashboard should be going green if it doesn't require a manual trigger: https://l10n-stage-sj.mozilla.org/shipping/dashboard?locale=km Is km now ready to be part of the beta trains?
catching up on bug triage: (In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #5) > km should be going green on the dashboard as hg for aurora and beta are now > matching. > > The dashboard should be going green if it doesn't require a manual trigger: > https://l10n-stage-sj.mozilla.org/shipping/dashboard?locale=km Yes, dashboards green. > Is km now ready to be part of the beta trains? km is part of betas since FF12.0b1. All depbugs are done. Investigating what, if anything, is left to do before Khmer officially ships in the FF12.0 release.
Depends on: 746485
Depends on: 747520
Firstly, congratulations team! You have worked and managed to get all the dependencies for this bug fixed, which means that productization for Khmer Firefox is all done. Please take a minute or two and read the next steps to follow. == Aurora == Every 6 weeks, we will update aurora repositories with new strings that will require some additional time spent on it. As you probably already know, we advise all localizers to use Aurora channel for all translations, so that we can merge them with Beta channel when needed without any regressions. So, please use Aurora as your primary working repo, and in case you're landing a fix to Beta channel, please port it back to Aurora too. Once the Aurora builds are available, please use them as much as you can for the purpose of testing your own translations and making sure everything is as it should be. == Bugs == Please check your dashboards every now and then to see if there are some bugs filed against Firefox in Khmer. You can check the status of your latest builds and some team info on l10n dashboard teams page at https://l10n.mozilla.org/teams/km . As the website evolved, you should start using that as your primary source of info related to localization. One other important thing to have in mind is webdashboard. We use webdashboard to show contributors bugs related to web localization for their locale. This is really important as we use our websites to promote localized Firefox builds. == Staying connected == You should also follow the Mozilla l10n newsgroup, http://www.mozilla.org/community/forums/#dev-l10n, available as mailing list, newsgroup or google group. The traffic isn't too high frequency. You'll find all announcements at http://www.mozilla.org/community/forums/#dev-l10n-announce . Those are vital to read, as they include things that the l10n-drivers want you to know and attend to. There's a third group, http://www.mozilla.org/community/forums/#dev-l10n-web, where we discuss web localization issues. That's a separate group as quite a few localization teams have dedicated volunteers for that. Another important thing is staying in touch with community and make yourself available for anyone who wants to contribute. So, if possible, get in touch with community on community forums, get feedback and possibly more volunteers. Enjoy and congratulations!
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.