Releases:Release Post Mortem:2016-02-17

From MozillaWiki
Revision as of 20:20, 11 February 2016 by Mtabara (talk | contribs) (Adding context for the roundtable)
Jump to navigation Jump to search

Meeting Details

« previous week | index | next week »
< most recent | upcoming >


Release Duty

  • FF 45 cycle: mtabara

Misc

Shipped

Thunderbird_45.0b1 (jlund/rail/callek/nick/mtabara)

  • victory!
  • instead of disabling updates I pointed Linux users to 44.0b1 and others to 45.0b1
  • TODO: awaiting decision as lack of TB equivalent watershed Firefox beta gtk3 rule in Balrog, please see email on TB-drivers email
  • build1
    • we had two win32 repacks failing
      • failed at repack_6/10 on win32 - retriggered, intermittent timeout
      • failed at repack_2/10 on win32 - retriggered
        • retriggered upon 'da' locale failed while submitting to balrog, specifically around the make_incremental_update.sh script
        • retriggered upon loosing slave instance
        • retriggered upon timeout
    • from tb-drivers mailing list: "We'll likely abandon build1 and go for build2 after getting some fixes"

  • build2:
    • "Same changesets as before, but buildbot changes merged to production."
    • gave up build 2 because of build error
  • build3:
    • intermittent errors:
      • failed at repack_7/10 on win32, automatic retry
      • failed at repack_3/10 on win32, automatic retry
      • failed at update_verify_beta_2/6 on linux64 - GTK3 known issue error
      • failed at update_verify_beta_2/6 on linux - GTK3 known issue error

Ongoing

Firefox 38.6.1 (mtabara/rail/nthomas)

  • awaiting 'Please push' email - everything looks good in terms of AV + update verify steps
  • for the font related issue mentioned in another thread, bug 1246093, we are building and testing a dot release for ESR, 38.6.1.
  • building from a relbranch with just the one sec fix
  • build1:
    • some intermittent errors:
      • antivirus check failed for a downloading issue when scanning, retriggered

Firefox 44.0.2 (mtabara/rail/nthomas)

  • build2:
    • intermittent errors for Firefox:
      • failed at firefox_antivirus, retriggered - intermittent download error for locale/partial
    • abandoned as there's a follow-up build3 coming underway
  • build3:
  • awaiting 'Please push' email - everything looks good in terms of AV + update verify steps
    • this build is needed to address a critical windows startup issue (backed out bug 1218473)
    • intermittent errors for Firefox:
      • few update verify failed for downloading issues

Fennec 44.0.2 (mtabara/rail/nthomas)

  • new security bug issue bug 1245724. 44.0.2 is underway for both desktop and mobile
  • build1:
    • stopped in order to add one more critical fennec issue and start a build 2
  • build2:
    • abandoned here for yet-another build to follow with a hotfix
    • intermittent errors:
      • Fennec 44.0.2 build2: build step failed on android-api-11 - failure to clone build/tools when the fingerprint didn't match. gps suspects AWS are rolling out new certs
  • build3:
    • abandonded here as buildbot-master73 froze our builds and was really slow today - given that there was too much room for human error to interfere, we'll follow-up with a fourth build.
  • build4:
    • intermittent errors:
      • [release-runner] WARNING: Reconfig exceeded 900m then 1800 seconds - looks like buildbot-master73 is naughty today and really slow hence it delayed the whole reconfig step
      • at least three builders have been grabbed by the same bm73 yet-again. We might end up in the same scenario as build3.

Roundtable

  • bhearsum: should we really be blocking shipping a chemspill release on what's new page configuration? I don't have opinion on this particular what's new page, but holding back in-the-wild fixes because of a what's new page seems bad

Context: 

20:12:19 <bhearsum> a question for the postmortem, maybe: should we really be blocking shipping a chemspill release on what's new page configuration?
20:12:55 <rail> we should stop showing it 
20:12:59 — ~mtabara agrees
20:13:19 <rail> we are about to ship esr45 :)
20:13:27 <bhearsum> i don't have opinion on this particular what's new page
20:13:55 <bhearsum> but holding back in-the-wild fixes because of a what's new page seems bad
20:14:59 <lizzard> we’r only holding it back for a short time
20:15:03 <lizzard> but good question....
20:15:32 <bhearsum> yeah, and it's only for esr in this case
20:15:41 <bhearsum> i doubt it made a practical difference for that userbase
20:15:51 <lizzard> For esr, i can’t imagine enterprise folks can deploy this so quickly as to mind an hour’s diference
20:15:52 <bhearsum> but if were the firefox release channel it might be a different story
20:17:26 <bhearsum> i guess it's also an important point that screwing up the WNP has more effect on the release channel

Action items

Retrieved from "https://wiki.allizom.org/index.php?title=Releases:Release_Post_Mortem:2016-02-17&oldid=1116874"