MozillaWiki

Compatibility/System Addon/Release Process: Difference between revisions

Page Discussion

Compatibility/System Addon/Release Process (view source)

Revision as of 12:25, 18 April 2023

1,981 bytes removed ,  18 April 2023
Add notes on how to uplift something in the firefox-android repo
(Version 102 is done.)
(Add notes on how to uplift something in the firefox-android repo)
 
(5 intermediate revisions by 2 users not shown)
Line 32: Line 32:


== Uplifting new interventions into Beta ==
== Uplifting new interventions into Beta ==
=== mozilla-central ===


For interventions that are a bit more urgent, you can skip one release cycle and uplift your intervention(s) into Beta. However, '''do not just request beta uplift''' for the patch you submitted to <tt>mozilla-central</tt>:
For interventions that are a bit more urgent, you can skip one release cycle and uplift your intervention(s) into Beta. However, '''do not just request beta uplift''' for the patch you submitted to <tt>mozilla-central</tt>:
Line 47: Line 49:
#* If your changes are more complicated, it might be a good idea to use the export tooling in our GitHub repo. You can <tt>git checkout</tt> the tag corresponding to the version currently shipping in Beta, and then <tt>git cherry-pick</tt> individual patches from <tt>main</tt> into your temporary branch. There is no need to publish/merge that branch upstream, as your beta rollout should never include any interventions that aren't also in the <tt>main</tt> branch anyway.
#* If your changes are more complicated, it might be a good idea to use the export tooling in our GitHub repo. You can <tt>git checkout</tt> the tag corresponding to the version currently shipping in Beta, and then <tt>git cherry-pick</tt> individual patches from <tt>main</tt> into your temporary branch. There is no need to publish/merge that branch upstream, as your beta rollout should never include any interventions that aren't also in the <tt>main</tt> branch anyway.
# Publish the beta patch to Phabricator and have a webcompat-reviewer rubberstamp the patch. It is a good idea to add a clear indication into the commit message saying that this patch is meant for the Beta branch. <tt>Bug 1234567 - Beta - Uplift v101 Interventions into v100 Beta.</tt> is an example.
# Publish the beta patch to Phabricator and have a webcompat-reviewer rubberstamp the patch. It is a good idea to add a clear indication into the commit message saying that this patch is meant for the Beta branch. <tt>Bug 1234567 - Beta - Uplift v101 Interventions into v100 Beta.</tt> is an example.
# Set the <tt>approval-mozilla-release?</tt> request flag, and explain in the comment why you think this patch should be uplifted to Beta.
# Set the <tt>approval-mozilla-beta?</tt> request flag, and explain in the comment why you think this patch should be uplifted to Beta.


A release manager will see your request. If your request is approved, the release managers will push your patch. You do not need to land it, or do anything else!
A release manager will see your request. If your request is approved, the release managers will push your patch. You do not need to land it, or do anything else!
=== firefox-android ===
For Android, the process is slightly different. After your Pull Request has been merged (and, ideally, tested), leave a comment in the Pull Request to tell the Mergify bot to create a backport PR (replace the version number with the target version number):
<tt>@mergify backport releases_v113</tt>
The bot will create a new PR and attach that PR to the original Bugzilla bug. You don't have to work on the GitHub PR, but you have to set the <tt>approval-mozilla-beta?</tt> flag on Bugzilla for the backport PR. After that, Release Management will proceed as usual.


== Uplifting new interventions into Release ==
== Uplifting new interventions into Release ==
Line 136: Line 146:


There is a [https://github.com/webcompat/web-bugs/issues?q=label%3Aaction-needssitepatch dedicated <tt>action-needssitepatch</tt> label on GitHub] as well as a [https://bugzilla.mozilla.org/buglist.cgi?product=Web%20Compatibility&component=Interventions&resolution=--- Bugzilla bug query] for sites that need interventions. 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).
There is a [https://github.com/webcompat/web-bugs/issues?q=label%3Aaction-needssitepatch dedicated <tt>action-needssitepatch</tt> label on GitHub] as well as a [https://bugzilla.mozilla.org/buglist.cgi?product=Web%20Compatibility&component=Interventions&resolution=--- Bugzilla bug query] for sites that need interventions. 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).
== Upcoming Releases ==
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1752990 Version 103] - Tom 2022-06-23 2022H1
== Past Releases ==
* Firefox 74 (v7) - Ksenia
* Firefox 75 (v8) - Dennis
* Firefox 76 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1621062 v9]) - Mike
* 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 79 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1637672 v12]) - Dennis
* 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 82 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1649244 v15]) - Tom
* Firefox 83 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1663967 v16]) - Dennis
* Firefox 84 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1663978 v17]) - Karl
* Firefox 85 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1663980 v18]) - Ksenia
* Firefox 86 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1686065 v19]) - Tom 2021-01-21 2021Q1
* Firefox 87 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1688792 v20]) - Dennis 2021-02-18 2021Q1
* Firefox 88 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1693824 v21]) - Karl 2021-03-18 2021Q1
* Firefox 89 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1702011 v22]) - Ksenia 2021-04-15 2021Q2
* Firefox 90 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1707797 v23]) - Tom 2021-05-27 2021Q2
* Firefox 91 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1714611 v24]) - Dennis 2021-07-08 2021Q2
* Firefox 92 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1720138 v25]) - Karl 2021-08-05 2021H2
* Firefox 93 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1720139 v26]) - Ksenia 2021-09-02 2021H2
* Firefox 94 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1720140 v27]) - Tom 2021-09-30 2021H2
* Firefox 95 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1720142 v28]) - Dennis 2021-10-28 2021H2
* Firefox 96 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1720143 v29]) - Karl 2021-12-02 2021H2
* Firefox 98 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1749436 v30]) - Ksenia 2022-02-03 2022H1
* Firefox 99 ([https://bugzilla.mozilla.org/show_bug.cgi?id=1752986 v31]) - Tom 2022-03-03 2022H1
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1752987 Version 100] - Dennis 2022-03-31 2022H1
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1752988 Version 101] - Dennis 2022-04-28 2022H1
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1752989 Version 102] - Ksenia 2022-05-26 2022H1


[[Category:Web Compatibility]]
[[Category:Web Compatibility]]
DenSchub
202

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/1242688...1246165"