Release:Release Automation on Mercurial:Updates through Shipping: Difference between revisions

m
→‎Betas/Final Releases: tweak to special ready to ship message
(try to improve wording on the "wait for final_verify")
m (→‎Betas/Final Releases: tweak to special ready to ship message)
Line 150: Line 150:
We have a builder that updates the right parts of Balrog to push a release live. When instructed, you can use "force build" to start it. (Balrog replaces pushing snippets, so should be done at the same time.)
We have a builder that updates the right parts of Balrog to push a release live. When instructed, you can use "force build" to start it. (Balrog replaces pushing snippets, so should be done at the same time.)


'''NOTE:''' this step requires a "double authorization" - appropriate sign off by QE or RelMan, ''and'' verifying that automation is ready (e.g. final_verify has completed).
'''NOTE:''' this step requires a "double authorization" - appropriate sign off by QE or RelMan, ''and'' verifying that automation is ready (e.g. 'ready to ship' notification).


Example buildbot URLs for the builder:
Example buildbot URLs for the builder:
Confirmed users
4,293

edits