Release Management/ESR Landing Process: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(139 intermediate revisions by 13 users not shown)
Line 1: Line 1:
'''Goal:''' We'd like to have a lightweight process that prevents "surprise" ESR landings at the 11th hour and makes sure ESR patches are created very soon after their related mainline patches
{{DISPLAYTITLE:ESR Landing Process}}


'''The ESR repo:''' https://hg.mozilla.org/releases/mozilla-esr10/
=== REPOS ===
The ESR repos can be found at https://github.com/mozilla-firefox/firefox/tree/esr{{ESR_CURRENT}}, for example, [https://github.com/mozilla-firefox/firefox/tree/esr{{ESR_CURRENT}} firefox-esr{{ESR_CURRENT}}]
See [https://whattrainisitnow.com/release/?version=esr ESR] on [https://whattrainisitnow.com/ whattrainisitnow] for the current supported ESR version.


'''More info about the ESR:''' https://wiki.mozilla.org/Enterprise/Firefox/ExtendedSupport:Proposal and https://www.mozilla.org/en-US/firefox/organizations/
===More info about the ESR===


'''What should land on mozilla-esr10:''' Security and some major stability fixes when they're landed/merged onto mozilla-beta, or fixes for regressions specific to the ESR
* https://support.mozilla.org/kb/firefox-esr-release-cycle
* https://www.firefox.com/browsers/enterprise/
* [https://www.mozilla.org/firefox/organizations/all/ Download]


'''The associated flags:'''
===What should land on firefox-esr===


approval-mozilla-esr10
Security and some major stability fixes when landed/merged onto firefox-beta, or fixes for regressions specific to the ESR. In the first few cycles of ESR we may be more flexible on these criteria. As the versions progress we limit this to security and high severity stability fixes.
* ?
* +
* -


tracking-esr10
Exception: If patches only make changes to tests, test harnesses, or anything else that does not affect the shipped builds, they may land with self approval (use a=testonly, a=npotb etc).
* ?
* -
* 11+
* 12+
* 13+
* ...


status-esr10
=== The associated flags===
* ?
* unaffected
* wontfix
* affected
* checkin-pending
* fixed
* verified


approval-mozilla-esrX: ''?'', ''+'', ''-''


'''The process:'''
tracking-esrX: ''?'', ''-'', ''{{BETA_VERSION}}+'', ''{{NIGHTLY_VERSION}}+'', ...


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:
status-esrX: ''?'', ''unaffected'', ''wontfix'', ''affected'', ''fixed'', ''verified''
* Set '''tracking-esr10''' to '''?'''
* Set '''status-esr10''' to '''affected''' if an ESR patch is still being worked on
* Set '''approval-mozilla-esr10''' to '''?''' and '''status-esr10''' checkin-pending if a patch is ''ready to land on mozilla-esr10''
2) Members of both Security and Release Management teams will triage tracking-esr10=?, 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-esr10''' flag will be set to '''+'''.
* In the case of an ESR-specific regression, we'll track for the next ESR release.
* 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-esr10 version, 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-esr10 flag to +}" to the commit message.
* After landing the patch, set status-esr10 to "fixed".
* Our beta period for the ESR will be to push this build to FTP a week early for qualification by enterprises.


esrX is the [https://whattrainisitnow.com/release/?version=esr ESR] version supported.


= ESR Triage Queries =
===The process===
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=2365492;field0-0-0=cf_tracking_esr10;query_format=advanced;type0-0-0=equals;value0-0-0=%3F ESR Nominations] - track for an upcoming ESR release, or don't track at all
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20approval-mozilla-esr10%3F ESR-10 approval requests] - approve/deny


* [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=nowordssubstr;list_id=4229122;field0-1-0=cf_status_esr10;field0-0-0=bug_group;chfieldto=Now;chfield=resolution;query_format=advanced;chfieldfrom=2012-08-25;value0-1-0=unaffected%20wontfix%20verified%20fixed%20affected;chfieldvalue=FIXED;type0-0-0=equals;value0-0-0=core-security Security bugs fixed on mainline] - mark the ESR as affected/unaffected, and set ESR tracking to Nightly version it was resolved on
# When an engineer believes that a stability bug or a security fix needs to be addressed for the ESR: Set '''status-firefox-esrX''' to '''affected'''. If there is more than one ESR version currently supported, then only set the relevant ESR versions as affected.
* [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=equals;list_id=4229229;field0-1-0=cf_status_esr10;field0-0-0=cf_tracking_esr10;query_format=advanced;value0-1-0=affected;type0-0-0=equals;value0-0-0={{BETA_VERSION}}%2B Bugs that need to be fixed on ESR this cycle] - follow up with the engineers
# When the patch is ready for uplift follow the standard [https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift Uplift Request Process]
* [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=equals;list_id=4229213;field0-1-0=cf_status_esr10;field0-0-0=cf_status_firefox{{BETA_VERSION}};value0-1-0=affected;value0-0-0=fixed%20verified;value0-2-0={{BETA_VERSION}}%2B;field0-2-0=cf_tracking_esr10;type0-0-0=anywordssubstr;type0-2-0=notequals;query_format=advanced May need to land now] - {{BETA_VERSION}}+ if necessary, or wontfix
# The Release Management team will monitor and process uplift requests during the Beta cycle of the corresponding mainline Firefox release.
 
= ESR Timeline and Activities =
See [https://wiki.mozilla.org/Release_Management/Release_Process_Checklist_Documentation#Beta_Checklist Release Checklist Documentation] for more details.  
 
 
=== Release Announcement Email ===
<pre>
Subject: Firefox ESR 115.12.0 released
 
We are pleased to announce that the Firefox ESR 115.12.0 release is now available for download at:
https://www.mozilla.org/firefox/organizations/all/
 
As always, we recommend that users keep up to date with the newest version
of Firefox ESR for the latest stability and security fixes.
 
Release notes for Firefox 115.12.0esr are available at:
https://www.firefox.com/firefox/115.12.0/releasenotes/
 
Associated security advisories are posted at:
https://www.mozilla.org/security/advisories/mfsa2024-26/
 
Thank you,
<name>
Firefox Release Manager
</pre>


[[category:Release_Management|E]]
[[category:Release_Management|E]]
[[Category:Release_Management:Processes|ESR]]

Latest revision as of 20:59, 11 February 2026


REPOS

The ESR repos can be found at https://github.com/mozilla-firefox/firefox/tree/esr140, for example, firefox-esr140 See ESR on whattrainisitnow for the current supported ESR version.

More info about the ESR

What should land on firefox-esr

Security and some major stability fixes when landed/merged onto firefox-beta, or fixes for regressions specific to the ESR. In the first few cycles of ESR we may be more flexible on these criteria. As the versions progress we limit this to security and high severity stability fixes.

Exception: If patches only make changes to tests, test harnesses, or anything else that does not affect the shipped builds, they may land with self approval (use a=testonly, a=npotb etc).

The associated flags

approval-mozilla-esrX: ?, +, -

tracking-esrX: ?, -, 150+, 151+, ...

status-esrX: ?, unaffected, wontfix, affected, fixed, verified

esrX is the ESR version supported.

The process

  1. When an engineer believes that a stability bug or a security fix needs to be addressed for the ESR: Set status-firefox-esrX to affected. If there is more than one ESR version currently supported, then only set the relevant ESR versions as affected.
  2. When the patch is ready for uplift follow the standard Uplift Request Process
  3. The Release Management team will monitor and process uplift requests during the Beta cycle of the corresponding mainline Firefox release.

ESR Timeline and Activities

See Release Checklist Documentation for more details.


Release Announcement Email

Subject: Firefox ESR 115.12.0 released

We are pleased to announce that the Firefox ESR 115.12.0 release is now available for download at:
https://www.mozilla.org/firefox/organizations/all/

As always, we recommend that users keep up to date with the newest version
of Firefox ESR for the latest stability and security fixes.

Release notes for Firefox 115.12.0esr are available at:
https://www.firefox.com/firefox/115.12.0/releasenotes/

Associated security advisories are posted at:
https://www.mozilla.org/security/advisories/mfsa2024-26/

Thank you,
<name>
Firefox Release Manager
Retrieved from "https://wiki.mozilla.org/index.php?title=Release_Management/ESR_Landing_Process&oldid=1256536"