canmove, Confirmed users
637
edits
Release Management/ESR Landing Process: Difference between revisions
Release Management/ESR Landing Process (view source)
Revision as of 23:23, 9 November 2015
, 9 November 2015second tracking-esr bullet should be status-esr instead
m (→Release Day: note about tracking flags and filing requests for bugzilla flag tweaking) |
m (second tracking-esr bullet should be status-esr instead) |
||
| Line 36: | Line 36: | ||
1) When an engineer believes that a stability bug needs to be addressed for the ESR, or a security fix that's landed on a branch affects the ESR: | 1) When an engineer believes that a stability bug needs to be addressed for the ESR, or a security fix that's landed on a branch affects the ESR: | ||
* Set '''tracking-esr{{ESR_CURRENT}}''' (and if we're in the middle of supporting 2 versions, then also tracking-esr{{ESR_NEXT}} to '''?''' | * Set '''tracking-firefox-esr{{ESR_CURRENT}}''' (and if we're in the middle of supporting 2 versions, then also tracking-firefox-esr{{ESR_NEXT}} to '''?''' | ||
* Set ''' | * Set '''status-firefox-esr{{ESR_CURRENT}}''' (and if we're in the middle of supporting 2 versions, then also status-firefox-esr{{ESR_NEXT}} to '''affected''' if an ESR patch is still being worked on | ||
* Set '''approval-mozilla-esr{{ESR_CURRENT}}''' (and if we're in the middle of support 2 versions, then also approval-mozilla-esr{{ESR_NEXT}} to '''?''' and '''status-esr{{ESR_CURRENT}}/{{ESR_NEXT}}''' checkin-pending if a patch is ''ready to land on mozilla-esr{{ESR_CURRENT}}/{{ESR_NEXT}}'' | * Set '''approval-mozilla-esr{{ESR_CURRENT}}''' (and if we're in the middle of support 2 versions, then also approval-mozilla-esr{{ESR_NEXT}} to '''?''' and '''status-firefox-esr{{ESR_CURRENT}}/{{ESR_NEXT}}''' checkin-pending if a patch is ''ready to land on mozilla-esr{{ESR_CURRENT}}/{{ESR_NEXT}}'' | ||
2) Members of both Security and Release Management teams will triage tracking-esr{{ESR_CURRENT}}/{{ESR_NEXT}}=?, and if agreement is that it's needed for the ESR, the tracking flag will be set to the first version of mainline Firefox that the patch is present in and the '''approval-mozilla-esr{{ESR_CURRENT}}/{{ESR_NEXT}}''' flag will be set to '''+'''. | 2) Members of both Security and Release Management teams will triage tracking-firefox-esr{{ESR_CURRENT}}/{{ESR_NEXT}}=?, and if agreement is that it's needed for the ESR, the tracking flag will be set to the first version of mainline Firefox that the patch is present in and the '''approval-mozilla-esr{{ESR_CURRENT}}/{{ESR_NEXT}}''' flag will be set to '''+'''. | ||
* In the case of an ESR-specific regression, we'll track for the next ESR release (e.g.: {{ESR_FUTURE}}). | * In the case of an ESR-specific regression, we'll track for the next ESR release (e.g.: {{ESR_FUTURE}}). | ||
* Why are we using mainline versions to track the ESR? According to the ESR proposal, a chemspill uses a minor version number, thus throwing off our tracking flags. Additionally, engineers shouldn't have to know what version of the ESR we're on. | * Why are we using mainline versions to track the ESR? According to the ESR proposal, a chemspill uses a minor version number, thus throwing off our tracking flags. Additionally, engineers shouldn't have to know what version of the ESR we're on. | ||
3) Once the mozilla-beta version matches the tracking-esr{{ESR_CURRENT}}/{{ESR_NEXT}} version(s), Security and Release Management teams will triage those bugs and make sure affected/checkin-pending fixes are landed at least 1 week prior to release so that we can go-to-build. | 3) Once the mozilla-beta version matches the tracking-firefox-esr{{ESR_CURRENT}}/{{ESR_NEXT}} version(s), Security and Release Management teams will triage those bugs and make sure affected/checkin-pending fixes are landed at least 1 week prior to release so that we can go-to-build. | ||
* Approval is required, so add "a={whoever set the approval-mozilla- | * Approval is required, so add "a={whoever set the approval-mozilla-esr{{ESR_CURRENT}} flag to +}" to the commit message. | ||
* After landing the patch, set status-esr{{ESR_CURRENT}}/{{ESR_NEXT}} to "fixed". | * After landing the patch, set status-firefox-esr{{ESR_CURRENT}}/{{ESR_NEXT}} to "fixed". | ||
* Our beta period for the ESR will be to push this build to FTP a week early for qualification by enterprises. | * Our beta period for the ESR will be to push this build to FTP a week early for qualification by enterprises. | ||
= ESR Triage Queries = | = ESR Triage Queries = | ||