Closed Bug 511510 Opened 10 years ago Closed 10 years ago
Enable nightly l10n updates for Firefox on 1
Axel wants this on 191 also, asserts there are dev + testers still on 191 who would use this. Blocked waiting for l10n.mk patches to be landed on 191.
(In reply to comment #0) > Axel wants this on 191 also, asserts there are dev + testers still on 191 who > would use this. > > Blocked waiting for l10n.mk patches to be landed on 191. To have the patch from bug 489313 landed we have to do a fake release of 1.9.2 (3.6b1) which is tracked on bug 512300
10 years ago
We are blocked on doing updates on slaves rather than on prometheus-vm
Depends on: 511967
Putting into the future list since I won't be able to look at it for at least the next 2 weeks. I will grab it if nobody does before I do.
Assignee: armenzg → nobody
Component: Release Engineering → Release Engineering: Future
Mass move of bugs from Release Engineering:Future -> Release Engineering. See http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.
Status: ASSIGNED → NEW
Component: Release Engineering: Future → Release Engineering
Priority: -- → P3
Axel: I'm ready to turn this on, but thought I'd confirm with you that it as still needed/wanted before I do.
Assignee: nobody → ccooper
Status: NEW → ASSIGNED
Priority: P3 → P2
Now that we're really stable on the 1.9.2 branch, I think we should spend the slave time on lorentz or something as worthwhile :-) Didn't check all the numbers, it might be a good call to offer a whitecard major update from 3.5.x nightlies to 3.6.x nightlies, not sure if that's at all possible?
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
The MU idea for nightlies is great. We don't currently have it even for en-US users but would make sense to have the ability.
(In reply to comment #7) > The MU idea for nightlies is great. We don't currently have it even for en-US > users but would make sense to have the ability. Filed bug 556515.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.