fennec_relpro.md

2017-02-28

• will need to uplift this patch to m-a, with kwierso's fix
• fennec hook - we'll need this, or equivalent, in releasetasks. alternative is manually triggering via releaseduty. commented in bug 1338161
• latest fennec candidates graph is green! task graph
  • patch pending r?
  • will need to land this on
    • autoland/inbound
    • m-c and uplift to m-a
  • currently have the beetmover workers pinned to my puppet env for staging beetmover push-to-candidates; we'll need a real puppet patch for dev+release beetmover creds+bucket info
  • anyone want to take a look at these builds/uploads? I don't know where the staging bucket is browsable via http, if at all see https://bugzilla.mozilla.org/show_bug.cgi?id=1343393#c10
  • hm, why are we pointing at 53.0-candidates instead of 53.0b1 ? should browser/config/version.txt say 53.0 or 53.0b1? should we be pointing at browser/config/version_display.txt ?
• beetmover scriptworkers are a bottleneck; we'll need to spin some [2?] more up
• i need to document any manual steps for releaseduty
• still need to create a mozilla-beta l10n-bumper patch, and enable it before merge day monday, and document manual l10n-bumping for releaseduty
• uplift to central + aurora the change from https://hg.mozilla.org/integration/mozilla-inbound/rev/ba2210b23ab3c96094450b9be4bb05e2089dba20 from bug 1343598
• land on inbound + uplift to central and aurora the https://hg.mozilla.org/projects/jamun/rev/b244e3ea2d982f79abc606ce364a854b1c881478 from 1343585