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.
I try to backport as many tickets as I can in half a day per week, following [wiki:org/teams/NetworkTeam/Backports the Network Team's backport process].
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:
* 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.
These exclusions will change with every [wiki:org/teams/NetworkTeam/CoreTorReleases major stable release], and some [https://gitweb.torproject.org/tor.git/ unstable releases].
=== Backports That Need Triage ===
These tickets need backport triage, usually by adding a consider-backport-* tag.
This query shows tickets even if they don't have any backport tags: that's a feature, not a bug. I like to see tickets that are in backport releases (or unspecified), so I can tag them for backport, put them in the right release, or close them.