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

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

827 bytes removed , 16 March 2015

canmove, Confirmed users

6,439

edits

@@ Line 202: / Line 202: @@
 In order to guard against accidents, this builder aborts unless a special property is set. You must enter a "shipit" property on the form, whose value is also "shipit".
-== Firefox RCs ==
-'''Until {{bug|1105485}} is fixed manual work needs to be done to prepare the RC's Balrog blob prior to pushing. See [https://wiki.mozilla.org/Releases/Firefox_35.0/BuildNotes#Updates_for_beta.2Fbeta-cdntest_2 old build notes for an example].'''<br/><br/>
-We generally publish RC builds to the beta channel. To do this you must manipulate the rule directly in Balrog:
-* Head over to [https://aus4-admin.mozilla.org/ the Balrog admin interface] (make sure you're using the 2.0 version).
-* Go to the "Rules" section
-* Search for "product:Firefox channel:beta"
-* Locate the rule for the plain "beta" channel and click its "Update" button.
-* Change the mapping to be the RC build that we're shipping (for example, Firefox-35.0-build3).
-* Click "Save Changes" to commit the change.
-* Announce on release-drivers.
 == Fennec ==