Fedora 33 Beta release is today. The schedule shows that the Final Freeze starts in one week, next Tuesday: https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html
We do have a built-in one week of slip in the Beta schedule ("Beta Target date #1") which doesn't cause an automatic Final release adjustment, but we slipped past that date now. However the Final schedule wasn't adjusted.
Is this correct? In the past (at least back when I was on FESCo) we've pushed out the Final Freeze to leave at least two weeks of development time between Beta and Final Freeze.
I asked @bcotton about this and it seems like that the beta slip never causes final schedule adjustment and I wanted to have FESCo confirmation if this is expected as it's FESCo that approves the schedule.
16:01 < kalev> bcotton: hey, I am looking at F33 schedule and it looks like there's only one week of development time before the Final Freeze 16:03 < kalev> bcotton: is the schedule correct? we slipped beta 2 weeks and past the built-in "Beta Target date #1", shouldn't that mean final freeze gets pushed out a week as well? 16:04 < pingou> kalev: nope, the beta release does not affect final release date 16:04 < bcotton> kalev: i was told "no, it does not" 16:04 < kalev> weird 16:04 < bcotton> if we had slipped an additional week, we probably would have moved back so that there would be a thaw 16:05 < misc> global warming everywhere, even on schedule 16:07 < kalev> bcotton: I'll go file a FESCo ticket just to make sure this is expected :)
Metadata Update from @ngompa: - Issue tagged with: meeting
I would definitely prefer not to slip. We've done such a good job of staying on schedule people are starting to expect it. :)
And as a practical matter, with the US election the week after the likely release date as it is, if we slip, we basically have to slip two weeks, and then it's dangerously close to the holidays.
It's my sense that even with the big changes, this is a pretty solid release already, so I'm not super worried about the short time.
Metadata Update from @churchyard: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.