Closed
Bug 586304
(fx-l10n-hy-AM)
Opened 14 years ago
Closed 12 years ago
[hy-AM] Firefox release tracker Armenian (getting out of beta)
Categories
(Mozilla Localizations :: hy-AM / Armenian, defect, P5)
Mozilla Localizations
hy-AM / Armenian
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Pike, Assigned: armenzg)
References
(Blocks 1 open bug)
Details
(Whiteboard: tracks getting Armenian out of beta state)
This is a tracker bug for releasing Firefox 4.0 hy-AM. This bug is not that detailed, but as we get particular work items, they should block this bug for tracking and discoverability.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → armenzg
Priority: -- → P4
Assignee | ||
Updated•14 years ago
|
Depends on: fx40-p12n-hy-AM
Assignee | ||
Comment 1•13 years ago
|
||
Shall we close this bug?
Assignee | ||
Updated•13 years ago
|
Priority: P4 → P5
Reporter | ||
Comment 2•13 years ago
|
||
Nope, this bug will get closed out once the Armenian localization makes it out of beta.
Assignee | ||
Comment 3•13 years ago
|
||
OK I didn't know that it was for that purpose. What would it require it to make it out of beta?
Reporter | ||
Comment 4•13 years ago
|
||
Get the blockers of this bug fixed, and positive community feedback. I recall that Milos talked to Robert, who wanted to wait for a bit back then. Not sure what the follow-up there is.
Assignee | ||
Updated•13 years ago
|
Summary: [hy-AM] Firefox 4.0 release tracker Armenian → [hy-AM] Firefox release tracker Armenian (getting out of beta)
Whiteboard: tracks getting Armenian out of beta state
Reporter | ||
Updated•13 years ago
|
Alias: fx40-l10n-hy-AM → fx-l10n-hy-AM
Comment 5•12 years ago
|
||
Firstly, congratulations team! You have worked and managed to get all the dependencies for this bug fixed, which means that productization for Armenian 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 Armenian. You can check the status of your latest builds and some team info on l10n dashboard teams page at https://l10n-stage-sj.mozilla.org/teams/bs . As the website evolves, you'll 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
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•