[CentOS-devel] [EPEL-devel] RHEL moving to issues.redhat.com only long term

Thu Mar 10 16:18:22 UTC 2022
Josh Boyer <jwboyer at redhat.com>

On Wed, Mar 9, 2022 at 5:05 PM Davide Cavalca via CentOS-devel
<centos-devel at centos.org> wrote:
> On Mon, 2022-03-07 at 12:44 -0500, 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.
> Thanks for sharing this Josh. Would you be able to expand on why Red
> Hat chose to use Jira specifically here, and what benefits do you
> forsee this switch will bring to CentOS down the road?

Red Hat has long used Jira in various parts of the company, with JBoss
and other products being heavy users for quite some time.  Within the
past few years we've consolidated a number of different instances into
the single issues.redhat.com instance.  That has enabled us to more
easily plan and coordinate across our product portfolio.

RHEL's decision is certainly informed by that same overall direction,
but also specifically influenced by the limiting factors of using
multiple tools to accomplish similar things.  We've been using
Bugzilla since Red Hat Linux days, and while it has served us well as
a defect tracking backend, it was never designed to handle the
complexity we have for planning and coordinating the varying scope of
work we have.  Aligning to a single tool will help us refine our
processes internally.

As for benefits to CentOS, or any of the other upstream projects we
interact with, we'll have to see.  I think the intention is to
minimize overall impact to start with, and then evolve our workflows
to bring further benefit where we can.  That being said, we are
certainly aware that we need to default to open issues to allow us to
collaborate directly in the open source manner we've long held to be
fundamental to our communities.  I expect that approach to behave very
similarly to how Bugzilla is used today.