#2369 Request: Postpone F32 Final Freeze by 3 ≤ N ≤ 7 days
Closed: Accepted 2 years ago by psabata. Opened 2 years ago by decathorpe.

I've had a lot of issues getting things into fedora 32 over the past week, with infrastructure problems delaying a lot of work because of:

  • koji(ra) newRepo tasks not getting run frequently enough (wait times exceed 2 hours in most cases)
  • bodhi refusing to submit new multi-build updates
  • bodhi refusing to edit existing multi-build updates
  • bodhi ejecting buildroot overrides prematurely (before their expiration time) - only noticed this one by accident

@churchyard and @ngompa had issues as well, and we think those issues warrant a slight postponement (for just a few days) of the Final Freeze for F32, just to get the things done that were blocked by infrastructure issues during the last week or so.


In order to make this actually possible, this would need to be approved today. Tagging with meeting.

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

2 years ago

Metadata Update from @churchyard:
- Issue tagged with: F32

2 years ago

Metadata Update from @ignatenkobrain:
- Issue untagged with: F32

2 years ago

+1

Now if releng accepts to do this on non Tuesday, I think +3 days are OK. Otherwise this needs to be a week.

Metadata Update from @churchyard:
- Issue tagged with: F32

2 years ago
* #2369 Request: Postpone F32 Final Freeze by 3 ≤ N ≤ 7 days  (contyk,
  15:02:40)
  * AGREED: Fedora 32 Final Freeze is posponed to Thursday 2020-04-09
    14:00 UTC (+9, 0, -0)  (contyk, 15:13:12)
  * ACTION: bcotton to update schedule  (bcotton, 15:13:24)

Metadata Update from @psabata:
- Issue untagged with: meeting
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

2 years ago

Metadata Update from @bcotton:
- Issue untagged with: F32
- Issue set to the milestone: Fedora 32

a year ago

Login to comment on this ticket.

Metadata