Compatibility/System Addon/Release Process: Difference between revisions
(→Intervention Release Owner Schedule: add some meta bugs) |
(→Interventions Release Rotations: Update page content) |
||
| Line 15: | Line 15: | ||
High priority interventions should be flagged immediately to the IRO who will then begin the process necessary to ship an off-train intervention. | High priority interventions should be flagged immediately to the IRO who will then begin the process necessary to ship an off-train intervention. | ||
== IRO Rotation Responsibilities == | |||
* Authoring, testing, landing high priority intervention patches | * Authoring, testing, landing high priority intervention patches | ||
* Authoring, testing, landing normal priority interventions | |||
* Requesting testing of high risk interventions from the WebCompat QA team | * Requesting testing of high risk interventions from the WebCompat QA team | ||
* Coordinating QA verification and release stakeholders (Balrog, AC, etc) for high priority interventions | * Coordinating QA verification and release stakeholders (Balrog, AC, etc) for high priority interventions | ||
| Line 24: | Line 25: | ||
* Backporting interventions from mozilla-central where necessary (see [https://github.com/mozilla/webcompat-addon/wiki/Backporting-a-mozilla-central-patch Backporting a Mozilla Central Patch]). | * Backporting interventions from mozilla-central where necessary (see [https://github.com/mozilla/webcompat-addon/wiki/Backporting-a-mozilla-central-patch Backporting a Mozilla Central Patch]). | ||
* Handling potential regression fallout from interventions | * Handling potential regression fallout from interventions | ||
* Add sitepatch-applied labels to web-bugs issues, as relevant. | |||
== Intervention Release Owner Schedule == | |||
For simplicity, we rotate on a per-release following the Nightly schedule at [[https://wiki.mozilla.org/Release_Management/Calendar|Firefox Release Calendar]]. | For simplicity, we rotate on a per-release following the Nightly schedule at [[https://wiki.mozilla.org/Release_Management/Calendar|Firefox Release Calendar]]. | ||
=== Upcoming Releases === | |||
* Firefox 80 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1647771 v13]) - Karl | * Firefox 80 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1647771 v13]) - Karl | ||
* Firefox 81 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1649243 v14])- Ksenia | * Firefox 81 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1649243 v14])- Ksenia | ||
* Firefox 82 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1649244 v15])- Tom | * Firefox 82 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1649244 v15])- Tom | ||
=== Past Releases === | |||
* Firefox 74 (v7) - Ksenia | * Firefox 74 (v7) - Ksenia | ||
| Line 41: | Line 43: | ||
* Firefox 77 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1625222 v10]) - Ksenia | * Firefox 77 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1625222 v10]) - Ksenia | ||
* Firefox 78 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1631858 v11]) - Mike | * Firefox 78 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1631858 v11]) - Mike | ||
* Firefox 79 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1637672 v12]) - Dennis | |||
[[Category:Web Compatibility]] | [[Category:Web Compatibility]] | ||
Revision as of 19:18, 10 July 2020
Interventions Releases
Release Process
The current draft document which describes the Interventions Release process can be found here: https://docs.google.com/document/d/1hyIv14aKDzGixuPz3rFHmVSXs-DlTFfJoleQxILwGws/edit#heading=h.kkurmbj28y1p
Comments are welcome in the document. Once finalized, the process will live here on this wiki page.
Interventions Release Rotations
Engineers on the Web Compatibility team will rotate on ownership of shipping new versions of our interventions addons, serving as an Intervention Release Owner (IRO). The process will follow a predictable 4 week schedule, mirroring the proposed 4 week Firefox release schedule.
During bug diagnosis, if a site is identified as a low priority intervention candidate, a label shall be added for the IRO to take care of during their rotation. Low priority interventions ride the trains without any need for uplifts or out of band shipping mechanisms. The expectation is that there will be a single regular low-priority release for each version of Firefox, driven by the IRO.
High priority interventions should be flagged immediately to the IRO who will then begin the process necessary to ship an off-train intervention.
IRO Rotation Responsibilities
- Authoring, testing, landing high priority intervention patches
- Authoring, testing, landing normal priority interventions
- Requesting testing of high risk interventions from the WebCompat QA team
- Coordinating QA verification and release stakeholders (Balrog, AC, etc) for high priority interventions
- Sending an intent-to-ship email for high priority intervention patches
- Landing patches in GitHub, Mozilla Central, and Android Components repos
- Requesting uplifts for interventions when necessary
- Backporting interventions from mozilla-central where necessary (see Backporting a Mozilla Central Patch).
- Handling potential regression fallout from interventions
- Add sitepatch-applied labels to web-bugs issues, as relevant.
Intervention Release Owner Schedule
For simplicity, we rotate on a per-release following the Nightly schedule at [Release Calendar].