Releases/Firefox 40.0/BuildNotes

Firefox build 1

• (RelMan) Ship the l10n milestone (build1 only)
• (RelMan) Submit to Ship It
• Set up whatsnew page
• Publish RC to Beta channel
• Push to mirrors
• Apply Throttling
• Verify throttling
• Publish in Balrog
• Post-release tasks

Issues

• linux64 repack 2/10 hang downloading mar file for the first locale

Downloading http://stage.mozilla.org/pub/mozilla.org/firefox/candidates/40.0-candidates/build1/linux-x86_64/en-US/firefox-40.0.tar.bz2 to firefox.tar.bz2
Downloading http://stage.mozilla.org/pub/mozilla.org/firefox/candidates/38.0.5-candidates/build4/update/linux-x86_64/bn-BD/firefox-38.0.5.complete.mar to firefox-38.0.5.bn-BD.complete.mar
Downloading http://stage.mozilla.org/pub/mozilla.org/firefox/candidates/35.0.1-candidates/build1/update/linux-x86_64/bn-BD/firefox-35.0.1.complete.mar to firefox-35.0.1.bn-BD.complete.mar
Downloading http://stage.mozilla.org/pub/mozilla.org/firefox/candidates/37.0.2-candidates/build1/update/linux-x86_64/bn-BD/firefox-37.0.2.complete.mar to firefox-37.0.2.bn-BD.complete.mar

command timed out: 2400 seconds without output ... program finished with exit code 247

• win32 repack 10/10 ran out of space with two locales to do. bug 1190644 to increase the requirement. It auto-retried but that was missed, and the standalone_repack job was used
• win32 repack 6/10 also failed, got 9.0G after asking for 7G. Auto-retried.
• firefox_release_updates failed with duplicate past-update lines, fixed with a config tweak
  • this probably caused the bustage in beta_final_verification and beta_update_verify (some but not all, strangely)
  • should we block on both updates builders completing ?
• 5 of the mac release update_verify failed with either an empty response, or completes that specified download.m.o instead of stage.m.o (despite being on the release-localtest channel). Not reproducible now, so must have been caching issues. We may need a delay at the end of the updates builder again