Changes

Jump to: navigation, search

Release Management/ESR Landing Process

149 bytes removed, 19:06, 19 July 2017
m
removing more unused templates
* 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}}''' to '''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-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}}).
* 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-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.
= ESR Triage Queries =
==CURRENT TEMPLATE VALUES==
 
[[Template:ESR_PREVIOUS|ESR_PREVIOUS (click to edit)]]: {{ESR_PREVIOUS}}
[[Template:ESR_CURRENT|ESR_CURRENT (click to edit)]]: {{ESR_CURRENT}}
[[Template:ESR_NEXT_BRANCH_DATE|ESR_NEXT_BRANCH_DATE (click to edit)]]: {{ESR_NEXT_BRANCH_DATE}} // Firefox {{ESR_NEXT}} beta branch date
 
[[Template:ESR_FUTURE|ESR_FUTURE]]: {{ESR_FUTURE}}
== ESR{{ESR_CURRENT}} ==
Canmove, confirm
629
edits

Navigation menu