Message 380193 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	erlendaasland
Recipients	erlendaasland, samuelmarks
Date	2020-11-02.08:09:02
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1604304543.05.0.359422105489.issue42242@roundup.psfhosted.org>
In-reply-to

Content
> [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

> [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

History
Date	User	Action	Args
2020-11-02 08:09:03	erlendaasland	set	recipients: + erlendaasland, samuelmarks
2020-11-02 08:09:03	erlendaasland	set	messageid: <1604304543.05.0.359422105489.issue42242@roundup.psfhosted.org>
2020-11-02 08:09:03	erlendaasland	link	issue42242 messages
2020-11-02 08:09:02	erlendaasland	create