Closed Bug 480598 Opened 13 years ago Closed 13 years ago
update ru changeset for b3
Axel wanted to look at the changes here, but want to get this to pick up the Yandex change completely for b3.
is changest supposed to be changeset or changes?
We can only take a really new changeset, unless we land the patch on the relbranch. Looking at the diff between the current B3 changeset and the current tip hg diff -r 79b83f5a615e toolkit/ netwerk/ dom/ security/manager/ browser/ extensions/reporter/ other-licenses/branding/firefox/ and https://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ru/pushloghtml?fromchange=79b83f5a615e, in particular the change in https://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ru/rev/803422dbe409 should get review. Unghost?
Attachment #364571 - Flags: review?(unghost)
Attachment #364571 - Flags: review?(unghost) → review+
Comment on attachment 364571 [details] [diff] [review] diff of toolkit and browser against current b3 changeset r=me
Summary: update ru changest for b3 → update ru changeset for b3
Taking this bug. I already landed this as http://hg.mozilla.org/build/buildbot-configs/rev/bcfdc3119e22 to make sure we get this in.
Assignee: nobody → l10n
Status: NEW → ASSIGNED
(In reply to comment #4) > I already landed this as > http://hg.mozilla.org/build/buildbot-configs/rev/bcfdc3119e22 to make sure we > get this in. Fine by me. All done here ?
If that's what you need to pick up the new changeset, yes. I don't know how the rel automation actually picks up the file in the end. Nick, mind marking this bug as FIXED if it is?
l10n-changesets is a local file on the master. I'll make sure it has been updated and master reconfig'd before b3 begins.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
(In reply to comment #7) This is done.
You need to log in before you can comment on or make changes to this bug.