Changes

Jump to: navigation, search

Release:Release Automation on Mercurial:Updates through Shipping

236 bytes added, 04:28, 25 January 2016
→‎Post-release tasks: Post-release process changes
= Post-release tasks =
Releases are considered 'shipped' when
* desktop - updates have been enabled, which is when the job release-$branch-update_shipping_$channel job has completed (eg release-mozilla-beta-update_shipping_beta)
* android - the apks have been uploaded to the Play Store
The post-release tasks should be run immediately afterwards.
 
== Mark as shipped on Ship It ==
'''<font color="red">NEW!</font>''' Releases need to be marked as shipped on Ship It after QA signs off. To do so, visit https://ship-it.mozilla.org/releases.html, find the release in question, and click the "Shipped!" button.
== postrelease builder ==
After pushes a release to Balrog, the The "post release" builder needs to be started with "force build". This builder will update bouncer aliases.
Example buildbot URLs for the builder:
NThomas
Confirm
4,293
edits
Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1114068"

Navigation menu