Closed Bug 597613 Opened 11 years ago Closed 10 years ago
[l10n-master] Branch for mozilla 2
Here is what we'll need to do for branching 2.0 right on the l10n-master/dashboard: - shut down twistd - shut down l10n-master and slave (when they're idle, of course) - land the attached patch, push, pull Enter magic, move the fx40x tree db object over to the new forest: fire up shell. from life.models import * t = Tree.objects.get(code='fx40x') f = Forest.objects.create(name='releases/l10n-mozilla-2.0', url='http://hg.mozilla.org/releases/l10n-mozilla-2.0/') t.l10n = f t.save() </magic> At this point, we need the en-US and l10n 2.0 branch repos to be up and ready. Start up the l10n-master and the slave, make sure the tree parsing works, https://l10n-stage-sj.mozilla.org/builds/waterfall?hours=1 will tell. Once that's fine, restart the twistd, twistd --umask=0022 get-pushes -s l10n_site.settings && tail -f twistd.log You want to tail -f the twistd.log on the l10n-master, too. Cross your fingers. MFBT.
SeaMonkey 2.1 will come from the mozilla-2.0 branch, so we'll start doing builds on that base shortly after the branch happens, trunk will go 2.2a1pre for the moment. We should file a followup for creating the correct l10n.ini files for that, we again will have that "two versions from one suite/ directory" approach once again there for some time.
Robert, did you get to create the l10n.ini's for comm-central?
We should probably do the update to compare-locales 0.9 (bug 601942) in the same go.
This should be what SeaMonkey needs here, right?
Attachment #481005 - Flags: review?(l10n)
Comment on attachment 481005 [details] [diff] [review] add branch ini for SeaMonkey Looks good.
Attachment #481005 - Flags: review?(l10n) → review+
Landed the SeaMonkey patch as http://hg.mozilla.org/comm-central/rev/76114da238e0 Please make this 2.0 branch one be sea21x actually and trunk sea22x once we actually have branched and this is being done.
Seamonkey was fixed in bug 646451. Marking FIXED.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.