If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[ml] Migrate CVS over to hg

RESOLVED FIXED

Status

Mozilla Localizations
ml / Malayalam
RESOLVED FIXED
9 years ago
9 years ago

People

(Reporter: Pike, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
We'll need a good point to migrate the content in cvs for ml 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

9 years ago
Hi Joyce, Ani, Joshy, Vivek and team:

The code freeze for Firefox 3.1 Beta 1 is in about two weeks from now, with string freeze coming next week Friday. 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 3.0 to 3.1 beta 1 pre, which should be doable.

Do you think you can move your work over to Hg from cvs and start working toward localizing Firefox 3.1.  Please let me know if you have any questions.

Kind regards,
Seth B

Comment 2

9 years ago
Hello Pike,

Can you plz migrate ml over to Hg. We would like to continue our work from Hg.
(Reporter)

Comment 3

9 years ago
The initial push is done, http://hg.mozilla.org/l10n-central/ml/pushloghtml.
I'll add Malayalam to the build in a bug 457287, and trigger initial builds. You can follow http://developer.mozilla.org/En/L10n_on_Mercurial and
work on a clone of the ml 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: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.