Releases/Firefox 38.2.0esr/BuildNotes
Contents
Build 1
-
(RelMan) Submit to Ship It
ABANDONED
Issues
Add update tests for older ESRs
This should've happened automatically, but because bug 1188014 didn't land before the release started, it didn't. Landed it before fixing the updates builder failure and retagged. The automation should take care of the rest.
Updates builder failure
Failed when bumping update verify config because 31.8.0esr was not in the patcher config, because the aforementioned patch hadn't landed yet. Retriggered the updates builder after that patch landed to get things going again.
Update verify failures
Update verify tests failed because of rules in Balrog that restricted ESR31 and earlier releases to the latest ESR31 release. I deleted those and retriggered the failed chunks.
Ship Updates
In addition to running the usual builder, the old ESR31 rule must be deleted, and the ESR38 updated to not restrict by version.
Build 2
Update patcher config before the release started
Due to the chemspill that came up, the patcher config needed a tweak before the release started. bug 1191832 has more information and the patch.
Set-up whatsnew page
A whatsnew page is required for users coming from non-ESR38 versions. To set-up, did the following:
- Downloaded the Firefox-38.2.0esr-build2 blob to laptop
- Copied to Firefox-38.2.0esr-build2-whatsnew.json
- Modified the new Firefox-38.2.0esr-build2-whatsnew as follows:
--- Firefox-38.2.0esr-build2.json 2015-08-07 09:58:51.453395955 -0400
+++ Firefox-38.2.0esr-build2-whatsnew.json 2015-08-07 10:02:48.622461689 -0400
@@ -1,6 +1,6 @@
{
"hashFunction": "sha512",
- "name": "Firefox-38.2.0esr-build2",
+ "name": "Firefox-38.2.0esr-build2-whatsnew",
"fileUrls": {
"esr-localtest": {
"partials": {
@@ -8906,5 +8906,7 @@
},
"detailsUrl": "https://www.mozilla.org/%LOCALE%/firefox/38.2.0/releasenotes/",
"displayVersion": "38.2.0esr",
- "platformVersion": "38.2.0"
-}
+ "platformVersion": "38.2.0",
+ "actions": "showURL",
+ "openURL": "https://www.mozilla.org/%LOCALE%/firefox/38.2.0/whatsnew/?oldversion=%OLD_VERSION%"
+}
- Uploaded to Balrog as Firefox-38.2.0esr-build2-whatsnew, with product set to Firefox and version to 38.2.0
- Added a new rule to Balrog to serve this blob for the appropriate users on esr-cdntest:
- product: Firefox
- channel: esr-cdntest
- rate: 100
- priority: 92 (higher than the existing esr-cdntest rule)
- version: <38.0
- update_type: minor
- mapping: Firefox-38.2.0esr-build2-whatsnew
- Verified with a couple of URLs:
- https://aus4.mozilla.org/update/3/Firefox/31.1.1/20140923184509/Linux_x86_64-gcc3/rm/esr-cdntest/default/default/default/update.xml?force=1 gets an update to 38.2.0 with a whatsnew page
- https://aus4.mozilla.org/update/3/Firefox/38.0/20140923184509/Linux_x86_64-gcc3/rm/esr-cdntest/default/default/default/update.xml?force=1 gets an update to 38.2.0 without a whatsnew page
We'll need a similar rule when we ship.
Publish in Balrog
This will be a bit more complicated because we're dropping ESR31 as part of this. Did the following:
- Set-up a rule similar to above to handle whatsnew pages for the "esr" channel (everything the same except channel)
- Adjusted throttling on the main "esr" channel rule to 25%
- Ran the update shipping builder as usual
- Deleted the rule pointing at "Firefox-31.8.0esr-build1"
- Removed the version condition and comment on the rule pointing at Firefox-38.1.1esr-build2
