Release Management/Nightly Respin: Difference between revisions

Release Management/Nightly Respin (view source)

Revision as of 07:49, 6 June 2018

148 bytes removed , 6 June 2018

Fix error in doc: blocking updates = releng, backout + respin = sheriffs

Pascalc

Confirmed users

1,255

edits

@@ Line 15: / Line 15: @@
 # File a bug with as much detail as possible about the regression / crash if a bug hasn't been filed yet
-# Ask sheriffs to stop automatic nightly updates because of the bug filed in step 1
+# Ask releng to stop automatic nightly updates because of the bug filed in step 1
 # Warn our users about the regression via our Twitter account and #nightly IRC channel, give the bug number.
 # Investigate to find the faulty patch via mozregression or stack traces for crashes
@@ Line 47: / Line 47: @@
 == Stopping automatic background updates ==
-If you think that a lot of people are going to be impacted by a regression, ask sheriffs to stop automatic updates. You can contact the on-call sheriff in the #sheriffs IRC channel. In case nobody is available, release engineering can do it (#releng channel).
+If you think that a lot of people are going to be impacted by a regression, ask releng to stop automatic update.
 Blocking automatic updates will not prevent new users to install Firefox Nightly from mozilla.org but it will mitigate greatly the impact on our existing user base.
-We can ask for automatic updates to be stoped for a specific OS.
+We can ask for automatic updates to be stopped for a specific OS.
 Most of the major regressions are reported immediately via our @FirefoxNightly Twitter account followers, usually when more than 2 people report a similar regression there is a high chance that it will be serious and stopping automatic updates should be done rapidly.