[issue42242] Backport SQLite trace API v2

[Erlend Egeberg Aasland]

Erlend Egeberg Aasland <erlend.aasland at innova.no> added the comment:

> [not sure if this is how you do backporting, a new issue and GH PR for each supported release tag?]

Backports are almost always created as backports of a specific GitHub pull request. The pull request is labelled as, for example, "needs backport to 3.9", and a bot will automatically try to cherry-pick the squashed commit to the target branch. So, if we wanted to backport GH-19581, we would do that directly from the original pull request over at GitHub. That will also preserve commit meta-data.

See also:
https://devguide.python.org/committing/?highlight=backport#backporting-changes-to-an-older-version

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue42242>
_______________________________________