Closed
Bug 1188014
Opened 10 years ago
Closed 10 years ago
merge esr31 and esr38 patcher configs
Categories
(Release Engineering :: Release Requests, defect)
Release Engineering
Release Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
Details
Attachments
(1 file)
33.69 KB,
patch
|
nthomas
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
The next scheduled ESR38 release will be the first one to upgrade ESR31 users. We need to merge the patcher configs together ahead of that to ensure that update verify tests happen.
Assignee | ||
Comment 1•10 years ago
|
||
We did a What's New Page for users when we did ESR24 -> ESR31, I'll find out if we're doing the same for ESR38.
Assignee | ||
Comment 2•10 years ago
|
||
Pretty simple copy over of the past-update lines and release blocks.
Last time we did this we had to set-up the WNP here (https://github.com/mozilla/build-tools/commit/090171f250d3a4a9d6fb1d5ba28ad213e324cde9), but I think that's no longer necessary...now that we have http://hg.mozilla.org/build/tools/rev/5cd91d786bb9 we should be able to set it in the release config template instead.
Looking over bug 1018694, it looks like we'll need an extra rule to handle esr31 vs. esr38 updates, so maybe we'll just go without a WNP page in the main blob, and add it after the fact.
Attachment #8641705 -
Flags: review?(nthomas)
Comment 3•10 years ago
|
||
Comment on attachment 8641705 [details] [diff] [review]
add old esrs to esr38 patcher config
>diff --git a/release/patcher-configs/mozEsr38-branch-patcher2.cfg b/release/patcher-configs/mozEsr38-branch-patcher2.cfg
>+ past-update 31.6.0esr 31.7.0esr esrtest releasetest esr
>+ past-update 31.7.0esr 38.1.0esr esrtest releasetest esr
> past-update 38.0esr 38.0.1esr esrtest releasetest esr
Please add a past-update line for 31.8.0esr too. Otherwise looks good.
Attachment #8641705 -
Flags: review?(nthomas) → review+
Assignee | ||
Updated•10 years ago
|
Attachment #8641705 -
Flags: checked-in+
Assignee | ||
Comment 4•10 years ago
|
||
This looks to be working fine.
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.
Description
•