* Josh Boyer: > As part of our continued 3 year major Red Hat Enterprise Linux release > cadence, RHEL 9 development is starting to wrap up with the spring > 2022 release coming soon. That means planning for the next release > will start in earnest in the very near future. As some of you may > know, Red Hat has been using both Bugzilla and Jira via > issues.redhat.com for RHEL development for several years. Our > intention is to move to using issues.redhat.com only for the major > RHEL releases after RHEL 9. Thanks for posting this publicly. > - Fedora Linux and EPEL have their own Bugzilla product families and > are not directly impacted in their own workflows by the choice to use > only issues.redhat.com for RHEL. > - There will be impacts on existing documentation that provide > guidance on requesting things from RHEL in various places like EPEL. > We will be happy to help adjust these. There is already an “FC” project on issues.redhat.com, into which Fedora bugs can be mirrored from bugzilla.redhat.com. Should we expose the mirror+ Bugzilla flag publicly, and make the FC project public, so that people can experiment with that? > If there are other impacts that you can think of, please raise them on > this thread. We’d like to ensure we’re covering as much as possible > as this rolls out. What is going to happen to the CentOS Mantis instance <https://bugs.centos.org/>? From the looks of it, it probably should just be switched off? Thanks, Florian _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
