We'll need a good point to migrate the content in cvs for [et] 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 Sander, 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 Estonian to be part of that release, so for that, we should migrate your cvs content over as soon as possible. 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 and is preferred. One thing you need to be aware of is that once we have copied your work over from cvs to hg, you'll need to manage two trees (hg and cvs) at the same time (decide which patches to land on which tree). 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. Please let us know what you think. We'd like you to move to Hg and that should happen pretty soon if possible.
i think i'm ready for Hg, i mean current cvs tree should be ready for it.. tho' i'm not sure what does it mean for me or how can i manage things in Hg, i hope i learn fast :)
The initial push is done, http://hg.mozilla.org/l10n-central/et/pushloghtml. I'll add Estonian 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 eo 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.