We'll need a good point to migrate the content in cvs for te over to an hg repository beneath http://hg.mozilla.org/l10n-central/ Please follow up to this bug when you think you're ready, setting the status whiteboard to a timestamp you'd consider good. Please don't land content in hg yourself before the initial migration is done, we want to make sure that the initial content in hg maps a cvs tag so that we can fix up hg annotate on the website to refer to cvs blame at one point.
Hi Arjun, Just an important update: Code freeze for Firefox 3.1 Beta 1 is in about two weeks from now, with string freeze coming next week Friday (September 26). We'd love you to be part of that release, so for that, we should migrate your cvs content over as soon as possible. Currently, there are some good 80 strings to be localized from FF 3.0 to FF 3.1 beta 1 pre, which should be doable. We know that you're likely going to get valuable feedback on the upcoming Firefox 3.0.2 (beta release) for Telugu, but that's still not ready to release from the code side, so waiting for that is probably not feasible. Once we have copied your work over from cvs to hg, you'll need to decide which patches to land on which tree, and land as planned separately. This is some additional work for you, but nevertheless, making Firefox 3.1 Beta 1 will help your release of Firefox 3.1 a good deal. Does that seem clear? If not, please ask. We do expect to have one more FF 3.1 beta cycle after FF B1, but only one, so making B1 is a really good idea. Please let us know what you think. We'd like you to move to Hg and that should happen pretty soon if possible. Kind regards, -sethb
Hi, I am ok with this migration process. I don't have any issues. Please do the needful. And for reference, you can find the telugu localization team over here https://wiki.mozilla.org/L10n:Localization_Teams#Telugu_.28te.2C_te-IN.29 Thanks Krishna.
The initial push is done, http://hg.mozilla.org/l10n-central/te/pushloghtml. I'll add Telugu to the build in bug 455731, and trigger initial builds. You can follow http://developer.mozilla.org/En/L10n_on_Mercurial and work on a clone of the te repo pulled via ssh or http. You'll push your changes as described on http://developer.mozilla.org/en/Mercurial_FAQ#How_do_I_check_stuff_in.3f
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.