On 12.06.2020 16:08, Ned Deily wrote:
On Jun 12, 2020, at 08:25, Ivan Pozdeev via Python-Dev <python-dev@python.org>
wrote:
Why not take a look at the list of open issues for 3.7 with PRs then? There are
702 as of now.
https://bugs.python.org/issue?%40sort0=creation&%40sort1=&%40group0=&%40group1=&%40columns=title%2Cid%2Cactivity%2Cstatus&%40filter=status%2Cversions%2Cstage&status=1&versions=21&stage=4&%40pagesize=50&%40startwith=0
Looking at open PRs is a good suggestion. Unfortunately, the version tags on
the bug tracker are not consistently maintained and updated. Just because there
is a PR attached to an issue doesn’t mean that it would be applicable today to
all the versions selected in the issue.
A more accurate approach is to look at open PRs that are either explicitly targeted for 3.7 or which have the “needs backport to 3.7” label. By those metrics, we currently have no open 3.7-specific PRs (the last was merged yesterday) and there are 60 open PRs with the 3.7 backport label. But even that number is high because some of those will end up not getting merged to master at all, and thus not backported, and others will be merged to master for 3.10 and perhaps to 3.9 but deemed inappropriate to backport to 3.8 and/or 3.7.
I would doubt the quality of tags maintenance at Github, too. E.g. https://github.com/python/cpython/pull/12131 is labeled 3.7 and 3.8 at
BPO but has no backport tags whatsoever at GH.
So the search you gave is clearly insufficient.
https://github.com/python/cpython/pulls?utf8=✓&q=is%3Apr+is%3Aopen+base%3A3.7
https://github.com/python/cpython/pulls?utf8=✓&q=is%3Apr+is%3Aopen+label%3A%22needs+backport+to+3.7%22
--
Ned Deily
n...@python.org -- []
--
Regards,
Ivan
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/55NOEOVOTQUJYXCKGEAULIDY7I22BPRJ/
Code of Conduct: http://python.org/psf/codeofconduct/
