BetaFE +1

BetaFE +1

The closer we're to final in Beta, the better, imo.

BetaFE +1

So, hmm, I'm not trying to be the annoying person around, but I'm curious - is there any actual benefit in having this newer python on the installation image, as compared to having it as a 0day (post-Beta) update? I'm sure there are some fixes inside, but there might also be some regressions. What's the most important argument for taking it in?

It's obviously a trade-off. By including it in the media, we might discover some bugs in beta that would otherwise be left not uncovered until the final release. But obviously, such a bug might be so severe, that the beta would be unusable for testing. If QA does not feel the timing is right, we can leave it out as a 0day update.

Yeah, it feels like a tricky cost vs. benefit tradeoff. I think I have to come down finely on the side of:

BetaFE -1

Currently I believe we're hoping for cutting the Beta release next week on Thursday. So at the moment the timing isn't really great, and I'm leaning towards
BetaFE -1
If this was a week earlier, I'd be fine with +1. Of course we never know whether we slip, but I think we have a decent chance making the release next week.

BetaFE -1

I do not think we'd not be able to trigger bugs between Beta and Final with this as an update. Python is heavily used.

Discussed during the 2023-09-11 blocker review meeting: [0]

The decision to delay the classification of this as a freeze exception was made as we have a split vote here, wecannot accept or reject it. We will punt this; if a clear consensus emerges in ticket voting it can be accepted or rejected.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-09-11/f39-blocker-review.2023-09-11-16.00.txt

BetaFE -1

I'll change my vote on this one, regarding what @humaton said on the meeting "the potential of introducing new bugz in the install process is just not worthed"

BetaFE -1

Release F39 is no longer tracked by BlockerBugs, closing this ticket.