On 04. 07. 22 19:03, Miro Hrončok wrote:
On 04. 07. 22 18:53, Pablo Galindo Salgado wrote:
Hi Miro,
>> Are all release blockers automatically blocking the next beta?
Yes.
>> Or does it mean this should not be released in final (and hence
neither rc)
versions?
Release blockers block also beta releases (if the RM decides so).
>> Would it make sense to release 3.11.0b4 with some not-yet-fixed
blockers?
No, the reason is that fixes can introduce more regressions and those
need to be fixed. If these fixes
are pretty big we would be risking big changes in the RC phase, which
we want to avoid. The idea is that
the fixes to critical problems reported on beta x can be tested on
beta x+1.
At the end of the day, this is all subjected to the judgement of the
release manager, and given how many
release blockers we have been getting and how many of these have been
reported past week *after* several
attempts to release the next beta, I have decided to wait.
Thanks. Understood.
Additionally, I am considering pushing the full release some months in
the future to allow for more betas, given
how unstable 3.11 is currently.
Some months sounds pretty big to me. Once the current beta is released,
I'd be great to see some updated release schedule. We have just updated
the main Python version Fedora 37 to 3.11 and we have some deadlines I'd
like not to miss.
https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html
2022-08-23 - Fedora 37 Beta Freeze
2022-10-04 - Fedora 37 Final Freeze
It would be really great to get something ABI stable at Beta Freeze and
at least an RC at the Final Freeze. If that is not realistic, we would
need to consider a revert.
Worse than a one-time revert. With the current schedule, the projects'
testing phases overlap so Fedora can test rebuilding all its Python
software with Python's alphas/betas. If the schedule is adjusted or made
unreliable, Fedora might need to add a six-month delay and rebuild with
final releases -- and find bugs much later.
_______________________________________________
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/FRAKKZNIVUL46JLPMRR76H24RSYRQMP7/
Code of Conduct: http://python.org/psf/codeofconduct/