On 4/4/2021 9:57 AM, Łukasz Langa wrote:
On 4 Apr 2021, at 11:34, Matthias Klose <d...@ubuntu.com
<mailto:d...@ubuntu.com>> wrote:
I always tested the release candidates, and built them for various Linux
architectures. And I'm filing issues marked as 'released-blocker'
when I see regressions introduced, it's up to the release manager >> to determine if such changes are intended or not.
Can you show us an example of a release-blocker issue you reported?
Searching creator: doko; priority: release blocker returns 19 issues,
from 3 to 20 years ago. That about 1/years but none for 3.8 or 3.9, for
which Łukasz is RM.
32232 36 months ago building extensions as builtins is broken in 3.7
has patch has PR closed
32233 40 months ago [3.7 Regression] build with --with-system-libmpdec
is broken has patch has PR closed
31016 43 months ago [Regression] sphinx shows an EOF error when using
python2.7 from the trunk closed
23968 55 months ago rename the platform directory from plat-$(MACHDEP)
to plat-$(PLATFORM_TRIPLET) has patch closed
26839 58 months ago Python 3.5 running on Linux kernel 3.17+ can block
at startup or on importing the random module on getrandom() has
patch closed
24226 71 months ago [3.5 Regression] unable to byte-compile the
attached IN.py closed
24162 71 months ago [2.7 regression] test_asynchat test failure on
i586-linux-gnu closed
23842 72 months ago SystemError: ../Objects/longobject.c:998: bad
argument to internal function has patch closed
22523 79 months ago [regression] Lib/ssl.py still references
_ssl.sslwrap has patch closed
17192 96 months ago libffi-3.0.13 import has patch closed
17579 97 months ago socket module in 2.7.4 raises error instead of
gaierror in 2.7.3 closed
14330 105 months ago don't use host python, use host search paths for
host compiler has patch closed
4303 149 months ago [2.5 regression] ctypes fails to build on
arm-linux-gnu closed
4469 149 months ago CVE-2008-5031 multiple integer overflows
closed
4552 150 months ago Doc/tools/sphinxext not included in the 2.6.1
tarball closed
4519 150 months ago .pyc files included in 2.6 and 3.0 release
tarballs closed
2601 157 months ago [regression] reading from a urllib2 file
descriptor happens byte-at-a-time closed
984880 203 months ago fix regression on 2.3 branch: Lib/threading has
patch closed
598996 226 months ago Failure building the documentation has patch
closed
The tradeoffs are the cost of bugfix release candidates (paid most by a
few people) versus the cost of the relative rare hotfix releases versus
the frequency of bugfix releases. I personally prefer a bugfix every 2
months without candidate to a bugfix every 4 months with one (these
being alternatives with the same work by the release crew).
A possible compromise would be to cut the release a couple of days ahead
and then pause while Matthias or anyone else runs tests. But I would
understand if Lukasz considered pausing to be worse than finishing the
release then and there. Or announce the upcoming release a week ahead
and ask committers to only merge PRs that could possibly break anything
to only do so with fresh CI tests. (Stale tests were one recent reason
a test-breaking PR got merged.)
--
Terry Jan Reedy
_______________________________________________
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/GEXTJNKD7IZL3J4M2ODESLJLLVAEQVKW/
Code of Conduct: http://python.org/psf/codeofconduct/
