160
edits
TestEngineering/Performance/Sheriffing/Tree FAQ: Difference between revisions
TestEngineering/Performance/Sheriffing/Tree FAQ (view source)
Revision as of 12:45, 16 January 2018
, 16 January 2018remove extra brackets
(Created page with "= Branch names and confusion = We have a variety of branches at Mozilla, here are the main ones that we see alerts on: * Mozilla-Inbound[-Non-PGO] * Fx-Team[-Non-PGO] * Mozill...") |
(remove extra brackets) |
||
| Line 32: | Line 32: | ||
= What is an uplift = | = What is an uplift = | ||
Every | 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. | ||
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 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. | ||