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. 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. Pablo Galindo Salgado On Mon, 4 Jul 2022 at 15:26, Miro Hrončok <mhroncok@redhat.com> wrote:
On 24. 06. 22 14:25, Pablo Galindo Salgado wrote:
Hi everyone,
A small update since the last communication from the release team regarding the status of Python 3.11.0b4.
Unfortunately, even if we have fixed most of the original release blockers and 4 more that appear during this week, we still have a bunch of release blockers to deal with. One of them has been reported today.
I would like to release the next beta next week if everything looks good, but there are also some items that need discussion...
I was thinking. Are all release blockers automatically blocking the next beta? Or does it mean this should not be released in final (and hence neither rc) versions? Would it make sense to release 3.11.0b4 with some not-yet-fixed blockers? Assuming those are not regressions that happened after 3.11.0b3 was released.
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok