These merge_ready tickets are in tor mainline, or torspec, and I am a maintainer. I need to check our [wiki:org/teams/NetworkTeam/MergePolicy Merge Policy] before merging, if I wrote or reviewed the code.
These merge_ready tickets are in tor mainline, or torspec, and I am a maintainer. I need to check our [Merge Policy](./org/teams/NetworkTeam/MergePolicy) before merging, if I wrote or reviewed the code.
I try to backport as many tickets as I can in half a day per week, following [wiki:org/teams/NetworkTeam/Backports the NetworkTeam's backport process].
I try to backport as many tickets as I can in half a day per week, following [the NetworkTeam's backport process](./org/teams/NetworkTeam/Backports).
Some tickets aren't considered for backport:
* [wiki:user/teor#TorMainline Mainline Merges]: master release tickets are merged by the mainline mergers, so the following milestones are hidden:
*[Mainline Merges](./user/teor#TorMainline): master release tickets are merged by the mainline mergers, so the following milestones are hidden:
* Tor: 0.4.4.x-final
* new backports: we try to test code in at least one alpha release before backporting it. You can see all the backports on the [wiki:user/teor/HiddenBackports Hidden Backports] page.
* new backports: we try to test code in at least one alpha release before backporting it. You can see all the backports on the [Hidden Backports](./user/teor/HiddenBackports) page.
These exclusions will change with every [wiki:org/teams/NetworkTeam/CoreTorReleases major stable release], and some [https://gitweb.torproject.org/tor.git/ unstable releases].
These exclusions will change with every [major stable release](./org/teams/NetworkTeam/CoreTorReleases), and some [unstable releases](https://gitweb.torproject.org/tor.git/).
=== Backports That Need Triage ===
### Backports That Need Triage
These tickets need backport triage, usually by adding a consider-backport-* tag.
...
...
@@ -146,29 +146,29 @@ This query shows tickets even if they don't have any backport tags: that's a fea