TestEngineering/Performance/Sheriffing/Tree FAQ: Difference between revisions

TestEngineering/Performance/Sheriffing/Tree FAQ (view source)

Revision as of 13:00, 16 January 2018

162 bytes removed , 16 January 2018

update paragraph

Igoldan

160

edits

@@ Line 31: / Line 31: @@
 = What is an uplift =
-Every [https://wiki.mozilla.org/RapidRelease/Calendar 6 weeks] we release a new version of Firefox.  When we do that, our code which developers check into the nightly branch gets uplifted (thing of this as a large [https://wiki.mozilla.org/Buildbot/Talos/Sheriffing/Tree_FAQ#What_is_a_merge merge]) to the Aurora branch.  Now all the code, features, and Talos regressions are on Aurora.  The same thing happens with Aurora, we uplift that to Beta.
+Every [https://wiki.mozilla.org/RapidRelease/Calendar 6 weeks] we release a new version of Firefox.  When we do that, our code which developers check into the nightly branch gets uplifted (thing of this as a large [https://wiki.mozilla.org/Buildbot/Talos/Sheriffing/Tree_FAQ#What_is_a_merge merge]) to the Beta branch.  Now all the code, features, and Talos regressions are on Beta.
-This affects the Talos Sheriff because we will get a big pile of alerts for Mozilla-Beta and Mozilla-Aurora.  These need to be addressed rapidly.  Luckily almost all the regressions seen on Mozilla-Beta will already have been tracked on Mozilla-Aurora, likewise all alerts that now show up on Mozilla-Aurora were already tracked on Mozilla-Central.
+This affects the Performance Sheriffs because we will get a big pile of alerts for Mozilla-Beta. These need to be addressed rapidly. Luckily almost all the regressions seen on Mozilla-Beta will already have been tracked on Mozilla-Inbound or Autoland.
 = What is a merge =