Closed
Bug 1340669
Opened 7 years ago
Closed 7 years ago
Update merge day and esr docs
Categories
(Release Engineering :: Release Requests, defect, P2)
Release Engineering
Release Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rail, Assigned: rail)
References
Details
https://wiki.mozilla.org/ReleaseEngineering/Merge_Duty (partially done) https://wiki.mozilla.org/ReleaseEngineering/How_To/Create_new_ESR_branch
|
Assignee | |
Updated•7 years ago
|
Priority: -- → P2
|
||
Comment 1•7 years ago
|
||
For the next ESR, we'll probably need to graft the browser_parsable_css.js ASAN disabling as well (or fold it in with the branding change). https://hg.mozilla.org/releases/mozilla-esr52/rev/af75aa20f686 Also, when grafting the branding change from an older ESR release, can we please update the commit message to reflect the right bug # for the current release? i.e. Not pointing at the ESR38 tracking bug for the ESR52 branding change landing. https://hg.mozilla.org/releases/mozilla-esr52/rev/df0931ac8b02
|
|
Assignee | |
Comment 2•7 years ago
|
||
https://wiki.mozilla.org/ReleaseEngineering/How_To/Create_new_ESR_branch https://github.com/mozilla/releasewarrior/blob/master/how-tos/new-esr-branch-setup.md
|
|
Assignee | |
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•