Closed Bug 1253505 Opened 10 years ago Closed 10 years ago

Did we mean to release Win64 on esr45?

Categories

(Release Engineering :: Release Automation, defect)

Product:
Release Engineering
Component:
Release Automation
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: philor, Unassigned)

References

Details

http://archive.mozilla.org/pub/firefox/candidates/45.0esr-candidates/build1/ says we didn't do a Win64 candidate, but I think our general story for platform support on an esr is that it gets whatever we are doing when we do the normal release for that branch, which would mean we did want to.
Very good point. We also should add something like http://hg.mozilla.org/build/buildbot-configs/file/tip/mozilla/release-firefox-mozilla-release.py.template#l40 to handle some exceptions properly. And once we on this, it'd be great to copy http://hg.mozilla.org/build/tools/file/tip/release/patcher-configs/mozEsr38-branch-patcher2.cfg to mozEsr45-branch-patcher2.cfg so we can generate update information for the future. After a couple of cycles we would need to update the file with information about esr38 releases happened between the initial copy and that moment. This would simplify our update situation.
I don't see why not.
I have 2 patches in the tracking bug 1237094. We'll need another build though.
We have triggered a follow-up Firefox-45.0esr-build2 to address the win64 enabling. Thanks for the heads-up on this.
LGTM in build2
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.