Releases/Firefox 37.0/BuildNotes

From MozillaWiki
Jump to: navigation, search

Firefox

Build 1

Checklist

Restart failed release updates builder

The release channel updates builder failed because it lost a push race to the beta channel one. bug 1105485 increased the chance of hitting this.

Manually force "ready for beta-cdntest" and "beta final verification" builders

An error in the patch from bug 1105485 caused these not to fire automatically. They had to be forced. The release equivalents will need forcing too, but not until after we push to mirrors.

Manually rebuild "tr" locale

This locale took a change after the en-US build started (bug 1146351) and we chose to rebuild only this locale rather than do a build2. This was done cowboy-style, cribbing off of the extremely outdated notes at https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Troubleshooting#Re-spinning_a_single_locale for some tips:

  • Retagged http://hg.mozilla.org/releases/l10n/mozilla-release/tr/ to pick up the change (flod did this, because bhearsum's hg account doesn't have permission to push to it).
  • Triggered a standalone repack for this locale for each platform to generate new bits
  • Retriggered update verify chunk #1 for each platform to verify them
  • Retriggered "checksums" builder to update *SUMS files
  • Decided not to rerun AV because the cost/benefit wasn't worthwhile.

The checksums builder "failed" because contrib dirs existed already, but it got far enough along to replace the checksums files, so it's good enough for our purposes.

Retrigger failed release channel update verify builders

A few chunks of these failed because they were running at the same time as the "tr" locale respin. Retriggered them, still awaiting results.

Set-up whatsnew page

  • Downloaded "Firefox-37.0-build1" blob to my laptop.
  • Renamed to "Firefox-37.0-build1-no-whatsnew", and removed "openURL" and "actions" from it.
  • Uploaded the new blob to Balrog

Still need to adjust the rules to set-up the locales correctly, that's blocked on bug 945179 being in production.

  • Added new rules for special locales to point to Firefox-37.0-build1, existing rules pointed at Firefox-37.0-build1.
  • tested by bensternthal on release-localtest
  • tweak by nthomas for not-special locales on release-localtest (aka the icelandic issue)
  • signed off by bensternthal

But we'll need to do it again for RC2.

tr updates failure

KaiRo found that tr was failing to update on windows, and on inspection the CDN serves a complete mar with incorrect hash & size. Mozmill only tests windows but we repacked all platforms so assumed it was a wider issue.

  • added a rule to block tr updates on channel=beta*
  • bug 1147616 to purge CDN
  • Akamai never cleaned up properly, but we're doing a build2 so the problem will go away then

Build 2

Checklist

Set-up whatsnew page

  • after linux64 build finished pointed locale-specific rules to Firefox-37.0-build2, so that update verify works
  • Downloaded "Firefox-37.0-build2" blob to my laptop.
  • Renamed to "Firefox-37.0-build2-no-whatsnew", and removed "openURL" and "actions" from it.
  • Uploaded the new blob to Balrog
  • Pointed non-locale-specific rules for release-{localtest,cdntest} to the new blob

Fix beta update verify

The block for the Turkish locale (see above, repack + CDN purge) caused 'no update found' errors for build2. Removed the rule in Balrog, but by then everything had failed except for release-mozilla-release-{macosx64,win32}_update_verify_beta_1/6. Reran the 22 of them. [Actually should have changed the channel from beta* to beta, to avoid failing downloads until RC2 is shipped]

Manually force "ready for beta-cdntest" and "beta final verification" builders

A (new and different) error in the patch from bug 1105485 caused these not to fire automatically. They had to be forced again. The release equivalents will need forcing too, but not until after we push to mirrors.

Publish by hand

For this release, the "default" rule in Balrog had to be pointed at the no-whatsnew blob, so we couldn't use the "update shipping" builder. To publish, did the following:

  • Created a new rule for the whatsnew locales by duplicating the release-cdntest one and adjusting the channel. It had the following data:
    • Product: Firefox
    • Channel: release
    • Mapping: Firefox-37.0-build2
    • Rate: 25
    • Priority: 91
    • Locale: en-US,en-GB,de,pt-BR,id,fr,es-ES,es-MX

Then I deleted the rule that was in place for 36.0 whatsnew pages. Finally, repointed the "default" Firefox release channel rule to the Firefox-37.0-build2-no-whatsnew blob and changed its rate to 25%. Any locales not included in the newly created rule above will fall through to it.

The order of operations is important here -- if the "default" rule was updated before the new one was created some users on the listed locales would not have received a whatsnew page.

Fennec

Build 1

Checklist

Burmese locale (my) missing

New for this release in Fennec, and not used for desktop, so wasn't synced over during the merge. Pike fixed that up, and bug 1147667 to improve the process as more mobile-only locales are coming.

Didn't get email about the failure, accidentally noticed it on ship-it.

Retrieved from "https://wiki.mozilla.org/index.php?title=Releases/Firefox_37.0/BuildNotes&oldid=1065575"