Releases/Firefox 41.0/BuildNotes: Difference between revisions
< Releases | Firefox 41.0
Jump to navigation
Jump to search
(→Release build3: published to balrog) |
(→Issues: post release issues for desktop) |
||
| Line 81: | Line 81: | ||
* build3 | * build3 | ||
** beta_final_verification failed for Firefox 41.0 build3 | ** beta_final_verification failed for Firefox 41.0 build3 | ||
*** | ** post_release failed: | ||
*** reason: post-release partner steps failed becasue we disabled partner repacks for this release | |||
*** resolution: disable post-release partner steps, re-tag, re-trigger: http://hg.mozilla.org/build/buildbot-configs/rev/faab86c39906 | |||
Revision as of 18:14, 22 September 2015
Fennec (RC not beta10)
Release build1
(RelMan) Ship the l10n milestone (build1 only)(RelMan) Submit to Ship It
gave up here as we are not shipping build1 as a release. we are doing a build2
Release build2
(RelMan) Ship the l10n milestone (build1 only)(RelMan) Submit to Ship It
gave up here as we are not shipping build1 as a release. we are doing a build3
Release build3
(RelMan) Ship the l10n milestone (build1 only)(RelMan) Submit to Ship It- Push to mirrors
- Post-release tasks
Firefox
Release build1
(RelMan) Ship the l10n milestone (build1 only)- (RelMan) Submit to Ship It
Set up whatsnew pageno new what's new pagePublish RC to Beta channel
gave up here as we are not shipping build1 as a release. we are doing a build2
Release build2
(RelMan) Ship the l10n milestone (build1 only)- (RelMan) Submit to Ship It
Set up whatsnew pageno new what's new pagePublish RC to Beta channel
gave up here as we are not shipping build1 as a release. we are doing a build3
Release build3
(RelMan) Ship the l10n milestone (build1 only)- (RelMan) Submit to Ship It
- Set up whatsnew page no new what's new page
- Publish RC to Beta channel
- Push to mirrors
- Apply Throttling
- Verify throttling
Publish in Balrog- Post-release tasks
Issues
- release-runner failed on first kick-off
- cause: firefox-38.0.5b3.complete.mar didn't exist so partial versions were wrong. we needed: 40.0.3build1,39.0build6,40.0.2build1,41.0b9build1
- resolution: re-submitted with correct partials based on ADI
- all fennec builds failed
- reason:
- bundleclone not working on linux/mock (https://bugzil.la/1191859)
- a change to log traceback errors if bundleclone fails (http://hg.mozilla.org/build/puppet/rev/04eb3e1f28c6)
- a multi_locale automation step (make package) that will fail if it parses error lines (like tracebacks from part 2)
- resolution: http://hg.mozilla.org/build/buildbot-configs/rev/65ef8a7712e3
- follow-up: discuss whether puppet deployments should be allowed on mon/tues of release week
- reason:
- api-11 fennec repack failures (chunks 1,2,3,7,8,10)
- reason: because of a mock package failed to install:
- 18:40:39 INFO - https://s3-us-west-2.amazonaws.com/mozilla-releng-mock-centos-us-west-2/mirrors/centos/6/latest/os/x86_64/GConf2-devel-2.28.0-6.el6.x86_64.rpm: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 500 Internal Server Error"
- resolution: the other chunks installed fine so it must have been a network issue between aws <-> mozilla. rebuilt the failed chunks
- follow-up: investigate network flows at the time of failure. might not be worth it.
- reason: because of a mock package failed to install:
- build3
- beta_final_verification failed for Firefox 41.0 build3
- post_release failed:
- reason: post-release partner steps failed becasue we disabled partner repacks for this release
- resolution: disable post-release partner steps, re-tag, re-trigger: http://hg.mozilla.org/build/buildbot-configs/rev/faab86c39906