On Thu, Mar 10, 2022 at 10:51 AM Simo Sorce <simo@xxxxxxxxxx> wrote: > > On Thu, 2022-03-10 at 09:44 -0500, Colin Walters wrote: > > > > On Mon, Mar 7, 2022, at 12:44 PM, Josh Boyer wrote: > > > Hi Fedora, CentOS, and EPEL Communities! > > > > > > 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. My only real concern here from a Fedora standpoint is security tracking. As it stands, the security team files fedora bugs for us linking back to the umbrella issue where most discussion happens. I would really miss that workflow if it were to break as unfortunately the kernel does get a number of CVEs to address (we are at 43 so far in 2022, we had 211 in 2021). > > I think it's unfortunate to replace the FOSS Bugzilla with > > proprietary software. I am eternally conflicted about this with > > respect to GitHub (xref > > https://blog.verbum.org/2020/12/03/still-on-github/ ) but...Jira is > > not as compelling of a user experience upgrade. > > > > A continual challenge related to this I feel is using the same > > software to track product bugs with potentially sensitive customer > > data in it, and public open development. > > > > To link these things, I quite commonly move Bugzilla discussion that > > has no need to be private to Github, because I know Github is always > > public (from our PoV). > > > > One thing that may help is to at least use different themes (e.g. > > blue colors for public CentOS issues, red for RHEL?) on > > issues.redhat.com. > > > > Long term if Bugzilla slowly morphs into only being used by Fedora, > > personally I'd prefer to have bugs/issues in gitlab instead. > > Given how we use bugzilla (we do not really use any big feature there) > in Fedora I would give a big +1 to use an issue tracker embedded in the > forge we use to store the packages (whether that is pagure, gitlab, > github, or something else). I would be very much against this move to integrate with the source forge. While It would probably work well for large parts of the distribution, it would be a bit of a nightmare for something like kernel with the number of bugs that it gets, and the rate of moving through things. I am not advocating for Jira here either, but at least what I currently see in gitlab and pagure would be a bit of a nightmare for me. I do very much like the idea of being able to perhaps tie bugs to kernel versions rather than Fedora releases though. It would be a useful feature in whatever we might choose if we were to move. Justin > Also I always resented that I need two separate accounts to deal with > Fedora packages, I think reducing that to host all in the same place > with the same authentication will also be a positive factor in > fostering collaboration, less barriers. It will also reduce > administrative overhead of having to configure components/ownership/etc > in multiple places and what not. > > Finally by having issues and code in the same place it means we can > easily connect commits/PRs/MRs to the issues meaning our issue tracker > a lot more useful, and will allow us to have better content also in our > updates, where today associating an update to an issue (a bz) is not > happening as well as it could. > > HTH, > Simo. > > -- > Simo Sorce > RHEL Crypto Team > Red Hat, Inc > > > > _______________________________________________ > 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 _______________________________________________ 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
