Compatibility/System Addon/Release Process
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.
Candidates for interventions
There is a list of sites as well as a Bugzilla bug query for sites that need interventions. In addition, the `type-uaoverride` label may be useful to look at. During a rotation, you should look at both of these sites and determine which are the most important to work on and ship (or close, if appropriate).
Lists of currently deployed interventions across the products and channels are available here https://arewehotfixingthewebyet.com/.
In addition, there is also a `sitepatch-applied` label that helps to keep track of existing interventions. Take care to add this to bugs after shipping a site patch.
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].