RHEL moving to issues.redhat.com only long term

[Josh Boyer]

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.

What does this mean for Fedora and CentOS?  This discussion is in part
to figure that out.  Based on some very brief analysis, the following
should hold:

- RHEL customers should continue to file support cases through the Red
Hat Customer portal, which will remain consistent regardless of the
backend tooling used.

- There is no imminent retirement of the Red Hat Bugzilla instance
being planned at this time.  RHEL 7, 8, and 9 will continue to use
bugzilla in some form and RHEL 9 has a very long lifecycle.

- 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.

- CentOS Stream contribution and bug reporting workflows will be
adjusted to use issues.redhat.com instead of bugzilla in the relevant
places.  This should apply to all versions of CentOS Stream for a
unified contributor workflow.  This will happen gradually as we
discover the best workflow to use.

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.

josh

[Davide Cavalca]

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?

Cheers
Davide

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

[Josh Boyer]

On Wed, Mar 9, 2022 at 5:05 PM Davide Cavalca via CentOS-devel
<centos-devel(a)centos.org&gt; 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.

josh

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

[Florian Weimer]

* 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

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

[Brian Stinson]

On Fri, Mar 11, 2022, at 04:55, Florian Weimer wrote:
>  * 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? 
Since we've moved CentOS Stream to bugzilla/jira I think it will make more and more
sense to look at deduplicating the number of bug trackers we have. CentOS Linux 7 bugs are
still nominally tracked in Mantis, though. 

We do not have active plans to retire bugs.centos.org yet. 

--Brian 

>
> Thanks,
> Florian
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> 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/[e-mail]
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure

[Thomas Stephen Lee]

On Mon, Mar 7, 2022 at 11:14 PM Josh Boyer <jwboyer(a)redhat.com&gt; 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.
>
>  What does this mean for Fedora and CentOS?  This discussion is in part
>  to figure that out.  Based on some very brief analysis, the following
>  should hold:
>
>  - RHEL customers should continue to file support cases through the Red
>  Hat Customer portal, which will remain consistent regardless of the
>  backend tooling used.
>
>  - There is no imminent retirement of the Red Hat Bugzilla instance
>  being planned at this time.  RHEL 7, 8, and 9 will continue to use
>  bugzilla in some form and RHEL 9 has a very long lifecycle.
>
>  - 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.
>
>  - CentOS Stream contribution and bug reporting workflows will be
>  adjusted to use issues.redhat.com instead of bugzilla in the relevant
>  places.  This should apply to all versions of CentOS Stream for a
>  unified contributor workflow.  This will happen gradually as we
>  discover the best workflow to use.
>
>  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.
>
>  josh 
Hi,

I tried logging in with my Red Hat id to see what it is.
I got the below message.
-----------------%<-----------------
SAML Single Sign On failed
Please contact your administrator and provide the tracker-id XXXXX or
log in at the login page.
SAML-Login failed: You’ve logged in with username user.name but you
already have an account on Jira, so please relogin with email_id
-----------------%<-----------------

Thanks

---
Lee

[Thomas Stephen Lee]

On Wed, Mar 16, 2022 at 12:00 PM Thomas Stephen Lee <lee.iitb(a)gmail.com&gt; wrote:
>  On Mon, Mar 7, 2022 at 11:14 PM Josh Boyer <jwboyer(a)redhat.com&gt; 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.
>  >
>  > What does this mean for Fedora and CentOS?  This discussion is in part
>  > to figure that out.  Based on some very brief analysis, the following
>  > should hold:
>  >
>  > - RHEL customers should continue to file support cases through the Red
>  > Hat Customer portal, which will remain consistent regardless of the
>  > backend tooling used.
>  >
>  > - There is no imminent retirement of the Red Hat Bugzilla instance
>  > being planned at this time.  RHEL 7, 8, and 9 will continue to use
>  > bugzilla in some form and RHEL 9 has a very long lifecycle.
>  >
>  > - 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.
>  >
>  > - CentOS Stream contribution and bug reporting workflows will be
>  > adjusted to use issues.redhat.com instead of bugzilla in the relevant
>  > places.  This should apply to all versions of CentOS Stream for a
>  > unified contributor workflow.  This will happen gradually as we
>  > discover the best workflow to use.
>  >
>  > 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.
>  >
>  > josh
>
>  Hi,
>
>  I tried logging in with my Red Hat id to see what it is.
>  I got the below message.
>  -----------------%<-----------------
>  SAML Single Sign On failed
>  Please contact your administrator and provide the tracker-id XXXXX or
>  log in at the login page.
>  SAML-Login failed: You’ve logged in with username user.name but you
>  already have an account on Jira, so please relogin with email_id
>  -----------------%<-----------------
>
>  Thanks
>
>  ---
>  Lee 
Issue resolved by Red Hat support.
Now I am able to log in.

---
Lee

[Thomas Stephen Lee]

Hi,

I am trying to request a package for RHEL 9, but I cannot find RHEL
under Projects at issues.redhat.com.
What is the correct project for RHEL 9 ?

Thanks

---
Lee


On Mon, Mar 7, 2022 at 11:14 PM Josh Boyer <jwboyer(a)redhat.com&gt; 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.
>
> What does this mean for Fedora and CentOS?  This discussion is in part
> to figure that out.  Based on some very brief analysis, the following
> should hold:
>
> - RHEL customers should continue to file support cases through the Red
> Hat Customer portal, which will remain consistent regardless of the
> backend tooling used.
>
> - There is no imminent retirement of the Red Hat Bugzilla instance
> being planned at this time.  RHEL 7, 8, and 9 will continue to use
> bugzilla in some form and RHEL 9 has a very long lifecycle.
>
> - 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.
>
> - CentOS Stream contribution and bug reporting workflows will be
> adjusted to use issues.redhat.com instead of bugzilla in the relevant
> places.  This should apply to all versions of CentOS Stream for a
> unified contributor workflow.  This will happen gradually as we
> discover the best workflow to use.
>
> 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.
>
> josh
> _______________________________________________
> epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org
> To unsubscribe send an email to epel-devel-leave(a)lists.fedoraproject.org
> 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/[e-mail]...
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure