fedora-qa

#514 RFE: track next release starting at branch in blockerbugs
Closed: Invalid Opened by mattdm.

Closed: Invalid
Reopen Issue

From this list discussion...

As we move into the No More Alphas world, and in trying to think about issues/bugs in a bigger picture than a single release (like, the "if we waive a blocker for some reason, it automatically applies to the next release" thing), it would be really helpful if we had a tracker for the next development release as soon as Rawhide branches (so, an F28 blockerbugs tracker when F27 branches).

This would be very valuable for my (and, I think, for Fedora Program Management)'s tracking of the planning/development/release cycle.

This sounds like a blockerbugs app RFE, you can create those directly in the project. I'll copy this one now, but please try to create any next tickets in the right places. Thanks!

Metadata Update from @jskladan:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

As I noted in https://pagure.io/fedora-qa/blockerbugs/issue/64#comment-456991 , I don't think this is actually an app RFE, but a request for another deployment of the app.

Yeah, it sounds like another deployment of the app is the easiest way.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/quality/tickets/issues/514

Please continue any further discussion there.
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.