fesco

#3184 Possibility of Delaying Final Freeze Start Date
Closed: Accepted by zbyszek. Opened by amoloney.

Closed: Accepted
Reopen Issue

Hello FESCo members,

I'm opening this ticket off the back of the F40 Beta Go/No-Go meeting. F40 Beta is GO - hurray! However, the release date is Tuesday 26th March and our Final Freeze date is scheduled for Tuesday 2nd April. I wanted to start the discussion with you early around the possibility of needing to delay the final freeze date because of this short time between the two events. The concern is there is a very narrow gap for users to use F40 Beta and report bugs, find and land fixes and generally refine the release for Final.
This ticket is to serve as a risk management attempt by starting the conversation as early as possible so we can prepare for the possible need to delay freeze.
Do you think it would be a good idea to have a pulse check sometime next week to see whether a delay might be needed? Or is it sufficient to let the release happen as per the schedule and delay the final release if it becomes apparent that this is in the best interest of the project?

Given how much things slipped up front, I would be inclined to also push the final freeze back at least a week.

Metadata Update from @sgallagh:
- Issue tagged with: meeting

I'm not entirely convinced that delaying the Final Freeze will actually improve the situation. It just means an additional week of unvetted changes landing. If we enter Freeze as originally planned, then any issues that come up from Beta testing can be accounted for as Blocker or Freeze Exceptions. Granted, it's possible that there will be a huge influx of these tickets and managing them as FEs might result in an unmanageable amount of overhead; in that case, is it possible (from a technical perspective) for us to temporarily lift a Freeze and mass-accept updates if that happens?

Yeah, it seems this is more or less the conclusion we reached when this was discussed previously. One week is enough to test, and if we wait longer, then we'll get a bigger influx of changes from people doing updates as usual. I think it's actually OK if we start the Final Freeze quickly. The important part is that we have time to resolve issues before Final, but actually being in Freeze helps with that: people cannot push new changes, so new issues are not being introduced, and we can always push changes that we know actually fix things.

I agree with @sgallagh and @zbyszek . I think it's fine to keep the freeze date as-is.

I selfishly would love more time between beta and final freeze to land some infrastructure things, but I definitely don't think thats worth itself to delay the freeze.

So, yeah, I'm ok with just keeping it short.

Perhaps we should/can mail a reminder email soon telling people that the final freeze is coming up very fast and to please test and stablize in the next week and a half?

This will be discussed during today's FESCo meeting.

This was discussed during today's meeting:
AGREED: REJECTED (-6, 0, 0)

Metadata Update from @zbyszek:
- Issue untagged with: meeting
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.