On the discussion of https://pagure.io/fedora-qa/blocker-review/issue/1633 it was noted that while Fedora has a long-standing policy of having the updates-testing repository enabled on the Beta (disabled shortly prior to GA), we don't actually have blocker criteria to validate this.
In order to remain consistent with existing history, I proposed that the criterion be added to future releases and that in the meantime FESCo should vote (via FastTrack) to block on having the updates-testing repository enabled on the default Beta installation.
(It has also been suggested that this could be a 0day blocker, having the first update after installing Beta enable the u-t repository, but I personally feel that this is inconsistent and adds a confusing delay.)
+1
I don't think this needs to be a criterion, honestly. Certainly not enough that we need FESCo to jump all over it, and I'd have appreciated a heads up or at least an @ .
The Beta criteria say that the system must be capable of installing updates, which gives us an appropriate mechanism to fix up issues in the default repo config with an update. I don't think it would be that terrible if we shipped a Beta with updates disabled then shipped an update to enable it. It's clearly much less bad than if we shipped Final with u-t enabled and then shipped an update to disable it.
As things stand we already granted the bug an FE and the fix is trivial so this will clearly get fixed, we do not need emergency FESCo action to make sure it's fixed. I wasn't expecting such alarums and excursions about this, tbh.
Don't think this met criteria for being approved in the fast-track process, so tagging for today's meeting (even though I think there's not much left that we need to do here).
Metadata Update from @decathorpe: - Issue untagged with: fast track - Issue tagged with: meeting
This was discussed during today's FESCo meeting:
INFO: The request to designate active state of updates-testing repo in F41 Beta as a FESCo blocker is withdrawn. (@decathorpe:fedora.im, 17:40:23)
Metadata Update from @decathorpe: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)