449834 - [bg] Migrate CVS over to hg

Status: RESOLVED FIXED

(Mozilla Localizations :: bg / Bulgarian, defect)

Description

[Axel Hecht [:Pike]]

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

Comment 1

[Staś Małolepszy :stas]

Hi Ognyan, 

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 Bulgarian 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.

Comment 2

[Ognyan Kulev]

Please migrate current CVS to hg. We definitely want Beta 1 to include Bulgarian.

Comment 3

[Axel Hecht [:Pike]]

The initial push is done, http://hg.mozilla.org/l10n-central/bg/pushloghtml.
I'll add Bulgarian 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 bg 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