Closed Bug 653731 Opened 9 years ago Closed 7 years ago
Bump the XPCOM version number when we bump mozilla-central versions
When we bump the version number on mozilla-central every six weeks, we should also bump the version number in xpcom/components/Module.h (e.g. http://hg.mozilla.org/mozilla-central/rev/f8b47b19a1e4) I'm not sure whether this version bump is done manually or with an automation script currently, but I'd like this task to be added to the automation or checklist we use for version bumps. Note: nothing needs to happen for the aurora (a1->a2) or beta (a2->final) version bumps, the XPCOM version stays the same for those.
OS: Linux → All
Priority: -- → P3
Hardware: x86_64 → All
(In reply to comment #0) > I'm not sure whether this version bump is done manually or with an automation > script currently, but I'd like this task to be added to the automation or > checklist we use for version bumps. This isn't handled by automation currently. The first Aurora version cut-over was handled by Christian, so maybe it's enough to get it on his radar for now? (http://hg.mozilla.org/mozilla-central/rev/a95d42642281)
8 years ago
No longer blocks: 627271
8 years ago
Are we planning on doing any of the release-train migrations via automation like this, if not I think this is an akeybl process thingy
This is already a part of our process and the merge mechanics document at http://mozilla.github.com/process-releases/draft/development_specifics/#branching. We can keep this open for future automation opportunities (bug 714371).
Mass move of bugs to Release Automation component.
Component: Release Engineering → Release Engineering: Automation (Release Automation)
mozilla-central version bumps are handled by the people doing the uplifting (the release management team, currently). We're not planning to automate that in general, so I think this is a WONTFIX.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.