This is a tracker bug for releasing Firefox ks. Your team's dashboard should be up on http://l10n.mozilla.org/teams/ks. 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.
You can find builds to test now on https://www.mozilla.org/en-US/firefox/developer/all/?q=kashmiri. There are quite a few technical errors reported on https://l10n.mozilla.org/teams/ks, probably on mozilla.locamotion.org, too. Now is a good time to fix those, and also get your community to use the builds and get feedback on the translation.
Given the lack of activity and community involvement, we're closing this bug as incomplete. Nothing is removed from repositories or tools, so we can restart the process after making sure there's a community able to support this effort.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.