Hi,

I filed on Bugzilla.
I wondered why there is no such option on issues.redhat.com (Jira ?).

Thanks

---
Lee

On Thu, May 19, 2022 at 11:08 AM Branislav Náter <bnater@redhat.com> wrote:
>
> Hi,
>
> On Thu, May 19, 2022 at 4:15 AM Thomas Stephen Lee <lee.iitb@gmail.com> wrote:
>>
>> 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 ?
>
>
> You have to file a bug for "distribution" component in Bugzilla.
>
> Regards
> B.
>
>>
>>
>> Thanks
>>
>> ---
>> Lee
>>
>>
>> On Mon, Mar 7, 2022 at 11:14 PM Josh Boyer <jwboyer@redhat.com> 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@lists.fedoraproject.org
>> > To unsubscribe send an email to epel-devel-leave@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/epel-devel@lists.fedoraproject.org
>> > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>> _______________________________________________
>> CentOS-devel mailing list
>> CentOS-devel@centos.org
>> https://lists.centos.org/mailman/listinfo/centos-devel
>
>
>
> --
> Branislav Náter
> Principal Quality Engineer, Stacks QE
> IRC: bnater at #qa #urt #brno
> Red Hat Czech s.r.o., Purkyňova 115, 612 00, Brno, Czech Republic
> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
> _______________________________________________
> CentOS-devel mailing list
> CentOS-devel@centos.org
> https://lists.centos.org/mailman/listinfo/centos-devel
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
https://lists.centos.org/mailman/listinfo/centos-devel