1247009 - (fx-l10n-ne-NP) [ne-NP] Firefox release tracker Nepali

Status: RESOLVED FIXED

(Mozilla Localizations :: ne-NP / Nepali (Nepal), defect)

Description

[Axel Hecht [:Pike]]

This is a tracker bug for releasing Firefox ne-NP.

Your team's dashboard should be up on http://l10n.mozilla.org/teams/ne-NP. The dashboard displays your project's status and helps you (and us) determine what's left to do. Follow it closely to track your Firefox localization progress. You will see this bug listed as part of your dashboard. This helps us to track your project's progress and provide visibilty to your work.

The "bugs" here are tracking individual items of work. Some of those will depend on the localization team driving them to completion, while others are for infrastructure that will be handled by Mozilla staff. I'll indicate who is responsible in each bug.

We'll also be using two terms for interacting with version control. That's commonly mercurial, or hg, in short. "commit" is used when talking about the actual 'hg commit' command, adding changes to the local version history. "landing" means to commit something and to use 'hg push' to push it from your local version history to the one on hg.mozilla.org, mozilla's server. That's when your changes are public, and make it into the builds mozilla generates, and puts on ftp.

If you're unsure what any of the terminology means, feel free to ask. Good places are http://www.mozilla.org/about/forums/#dev-l10n-new-locales or #l10n. Ask in public, you shouldn't assume that you're the only one with the question.

Comment 1

[Axel Hecht [:Pike]]

To community members interested in following the process here, feel free to watch the Nepali bugzilla component by going to https://bugzilla.mozilla.org/userprefs.cgi?tab=component_watch&product=Mozilla%20Localizations, and select the "ne-NP / ...." component.

Comment 3

[Axel Hecht [:Pike]]

One more comment on how to interact with https://mozilla.locamotion.org/ne/firefox/:

Please focus on making the translations of each goals consistent. Either full or not.

In particular, have a conversation inside your team about what to do with devtools. Keeping it in English might be the right localization, and having a few Nepali strings here and there could look worse than being consistently in English.

The goals of level 2 and higher should be something to consistently translate, though.

Comment 4

[Axel Hecht [:Pike]]

The builds are now enabled, and binaries will be generated each day. The switch landed after today's build, so tomorrow, the first builds will show up.

The dashboard at https://l10n.mozilla.org/teams/ne-NP is now live, too. And I've noticed a few old files that I manually removed, https://hg.mozilla.org/releases/l10n/mozilla-aurora/ne-NP/rev/da350b5330ef.

Comment 5

[Nootan Ghimire]

Thanks, We'll now use the dashboard to prioritize localizations.

Comment 6

[Axel Hecht [:Pike]]

Builds are up on https://ftp.mozilla.org/pub/firefox/nightly/latest-mozilla-aurora-l10n/, and soon will be on https://www.mozilla.org/en-US/firefox/developer/all/?q=nepali, which is easier to share. Bug  	1247015 will enable the latter link to work.

Comment 7

[Francesco Lodolo [:flod]]

We have Beta builds, and Nepali will ride the trains to release with 58.
https://www.mozilla.org/it/firefox/beta/all/?q=Nepali