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

Release:Release Automation on Mercurial:Updates through Shipping (view source)

682 bytes removed , 16 October 2014

→‎Generate RC to b1 snippets: We switched to Balrog, which handles this automatically

Confirmed users

4,293

edits

@@ Line 23: / Line 23: @@
 * When there are warnings about other snippets missing, a 'Warnings' log will be created and the step will be orange. These must be investigated and explained/fixed before any live snippets are pushed.
 * If any snippets differ in contents between the test and live channels a 'Diffs' log will be created and the step will be orange. The Diffs log will list the files which differ; the full diffs can be viewed in the stdio log. Any differences must be investigated and explained/fixed before any live snippets are pushed.
-== Generate RC to b1 snippets ==
-Until {{bug|908134}} yields full integration of release RC builds on the beta channel, we need some manual work for beta1 of a new cycle. We copy some snippets to provide a complete update from X-1.0build1, X-1.0build2,... up to the new X.0beta1. QA often uses the terminology 'release candidate' or RC for the X-1.0buildN builds.
-See these previous examples for what to do [[Releases/Firefox_32.0b1/BuildNotes#no_updates_from_previous_RC | 32.0b1]], [[Releases/Firefox_31.0b1/BuildNotes#Generate_30.0_RC_-.3E_31.0b1_update_paths | 31.0b1]]. '''You will need to update some versions and buildIDs''', ask nthomas/bhearsum/rail if you need support.
 = Update Verify =