Release Management/Nightly Respin: Difference between revisions

m
(Sheriffs are involved)
Line 47: Line 47:
== Stopping automatic background updates ==
== Stopping automatic background updates ==


If you think that a lot of people are going to be impacted by a regression, ask releng to stop automatic update.
If you think that a lot of people are going to be impacted by a regression, ask releng or relman 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.
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 stopped for a specific OS.
We can ask releng for automatic updates to be stopped for a specific OS and potentially set up a fallback update mechanism to the last good known builds.
 
Most of the time, it is Relman that stops update via Balrog, it stops updates for all OSes.


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.
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.
'''Note:''' Some members of the release management team have the technical knowledge and permissions to stop automatic updates.


== Asking for a back out of the patch  and new nightlies ==
== Asking for a back out of the patch  and new nightlies ==
Confirmed users
1,255

edits