#1283 [fedora-repos] updates-testing is not enabled when it should be | rhbz#2237651
Closed by blockerbot. Opened by blockerbot.

Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2237651 **
Information from BlockerBugs App:
2237651

Current vote summary

The votes have been last counted at 2023-09-11 15:01 UTC and the last processed comment was #comment-873568

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review
A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)


Definitely
BetaFE +1
and I'm not sure about the blocker, waiting for Adam's infinite knowledge of Fedora processes.

Also:
BetaFE +1
I...don't think we actually have a requirement that updates-testing be enabled at release, and I suppose it would be fairly easy to do it post-release. It's just a thing we usually do. It probably doesn't need to be a blocker.

BetaBlocker +1
BetaFE +1

I think this is the point on a beta release: testing things, and it's awkward not having testing repositories enabled on the "testing release".

The following votes have been closed:

BetaFE +1
BetaBlocker -1

This is not as serious and could be let known in CommonBugs.

BetaBlocker -1

I agree with @lruzicka

BetaBlocker -1

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

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

Log in to comment on this ticket.

Metadata