Closed Bug 449837 Opened 11 years ago Closed 11 years ago

[eo] Migrate CVS over to hg

Categories

(Mozilla Localizations :: eo / Esperanto, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Pike, Unassigned)

References

Details

We'll need a good point to migrate the content in cvs for eo 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.
Eduardo, 

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 Esperanto 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.
Ok Staś, Let's do it.  Axel, I guess now is a good time to migrate.

There is a small problem though,  I still don't have access to hg/cvs (Bug 453837).  But you can move ahead and, as soon as I have the account, I will apply the necessary patches to both trees.
I poked about the access, hopefully that should go quickly now.

The initial push is done, http://hg.mozilla.org/l10n-central/eo/pushloghtml. I'll add Esperanto to the build in bug 455731, and trigger initial builds, but for now, you can follow http://developer.mozilla.org/En/L10n_on_Mercurial and work on a clone of the eo repo pulled via http. To push your changes later you just add a default-push path to your hgrc, as described on http://developer.mozilla.org/en/Mercurial_FAQ#How_do_I_check_stuff_in.3f
Blocks: 455731
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.