<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 19, 2022 at 11:34 AM Thomas Stephen Lee <<a href="mailto:lee.iitb@gmail.com">lee.iitb@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
I filed on Bugzilla.<br>
I wondered why there is no such option on <a href="http://issues.redhat.com" rel="noreferrer" target="_blank">issues.redhat.com</a> (Jira ?).<br></blockquote><div>From my limited knowledge and from the initial announcement "Our intention is to move to using <a href="http://issues.redhat.com" rel="noreferrer" target="_blank">issues.redhat.com</a> only for the major RHEL releases __after__ RHEL 9." So currently bugzilla is the place to start (bugs are then mirrored to <a href="http://issues.redhat.com">issues.redhat.com</a> under RHELPLAN project).</div><div><br></div><div>B.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Thanks<br>
<br>
---<br>
Lee<br>
<br>
On Thu, May 19, 2022 at 11:08 AM Branislav Náter <<a href="mailto:bnater@redhat.com" target="_blank">bnater@redhat.com</a>> wrote:<br>
><br>
> Hi,<br>
><br>
> On Thu, May 19, 2022 at 4:15 AM Thomas Stephen Lee <<a href="mailto:lee.iitb@gmail.com" target="_blank">lee.iitb@gmail.com</a>> wrote:<br>
>><br>
>> Hi,<br>
>><br>
>> I am trying to request a package for RHEL 9, but I cannot find RHEL<br>
>> under Projects at <a href="http://issues.redhat.com" rel="noreferrer" target="_blank">issues.redhat.com</a>.<br>
>> What is the correct project for RHEL 9 ?<br>
><br>
><br>
> You have to file a bug for "distribution" component in Bugzilla.<br>
><br>
> Regards<br>
> B.<br>
><br>
>><br>
>><br>
>> Thanks<br>
>><br>
>> ---<br>
>> Lee<br>
>><br>
>><br>
>> On Mon, Mar 7, 2022 at 11:14 PM Josh Boyer <<a href="mailto:jwboyer@redhat.com" target="_blank">jwboyer@redhat.com</a>> wrote:<br>
>> ><br>
>> > Hi Fedora, CentOS, and EPEL Communities!<br>
>> ><br>
>> > As part of our continued 3 year major Red Hat Enterprise Linux release<br>
>> > cadence, RHEL 9 development is starting to wrap up with the spring<br>
>> > 2022 release coming soon. That means planning for the next release<br>
>> > will start in earnest in the very near future. As some of you may<br>
>> > know, Red Hat has been using both Bugzilla and Jira via<br>
>> > <a href="http://issues.redhat.com" rel="noreferrer" target="_blank">issues.redhat.com</a> for RHEL development for several years. Our<br>
>> > intention is to move to using <a href="http://issues.redhat.com" rel="noreferrer" target="_blank">issues.redhat.com</a> only for the major<br>
>> > RHEL releases after RHEL 9.<br>
>> ><br>
>> > What does this mean for Fedora and CentOS? This discussion is in part<br>
>> > to figure that out. Based on some very brief analysis, the following<br>
>> > should hold:<br>
>> ><br>
>> > - RHEL customers should continue to file support cases through the Red<br>
>> > Hat Customer portal, which will remain consistent regardless of the<br>
>> > backend tooling used.<br>
>> ><br>
>> > - There is no imminent retirement of the Red Hat Bugzilla instance<br>
>> > being planned at this time. RHEL 7, 8, and 9 will continue to use<br>
>> > bugzilla in some form and RHEL 9 has a very long lifecycle.<br>
>> ><br>
>> > - Fedora Linux and EPEL have their own Bugzilla product families and<br>
>> > are not directly impacted in their own workflows by the choice to use<br>
>> > only <a href="http://issues.redhat.com" rel="noreferrer" target="_blank">issues.redhat.com</a> for RHEL.<br>
>> > - There will be impacts on existing documentation that provide<br>
>> > guidance on requesting things from RHEL in various places like EPEL.<br>
>> > We will be happy to help adjust these.<br>
>> ><br>
>> > - CentOS Stream contribution and bug reporting workflows will be<br>
>> > adjusted to use <a href="http://issues.redhat.com" rel="noreferrer" target="_blank">issues.redhat.com</a> instead of bugzilla in the relevant<br>
>> > places. This should apply to all versions of CentOS Stream for a<br>
>> > unified contributor workflow. This will happen gradually as we<br>
>> > discover the best workflow to use.<br>
>> ><br>
>> > If there are other impacts that you can think of, please raise them on<br>
>> > this thread. We’d like to ensure we’re covering as much as possible<br>
>> > as this rolls out.<br>
>> ><br>
>> > josh<br>
>> > _______________________________________________<br>
>> > epel-devel mailing list -- <a href="mailto:epel-devel@lists.fedoraproject.org" target="_blank">epel-devel@lists.fedoraproject.org</a><br>
>> > To unsubscribe send an email to <a href="mailto:epel-devel-leave@lists.fedoraproject.org" target="_blank">epel-devel-leave@lists.fedoraproject.org</a><br>
>> > Fedora Code of Conduct: <a href="https://docs.fedoraproject.org/en-US/project/code-of-conduct/" rel="noreferrer" target="_blank">https://docs.fedoraproject.org/en-US/project/code-of-conduct/</a><br>
>> > List Guidelines: <a href="https://fedoraproject.org/wiki/Mailing_list_guidelines" rel="noreferrer" target="_blank">https://fedoraproject.org/wiki/Mailing_list_guidelines</a><br>
>> > List Archives: <a href="https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org" rel="noreferrer" target="_blank">https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org</a><br>
>> > Do not reply to spam on the list, report it: <a href="https://pagure.io/fedora-infrastructure" rel="noreferrer" target="_blank">https://pagure.io/fedora-infrastructure</a><br>
>> _______________________________________________<br>
>> CentOS-devel mailing list<br>
>> <a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a><br>
>> <a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/centos-devel</a><br>
><br>
><br>
><br>
> --<br>
> Branislav Náter<br>
> Principal Quality Engineer, Stacks QE<br>
> IRC: bnater at #qa #urt #brno<br>
> Red Hat Czech s.r.o., Purkyňova 115, 612 00, Brno, Czech Republic<br>
> <a href="http://redhat.com" rel="noreferrer" target="_blank">redhat.com</a> | TRIED. TESTED. TRUSTED. | <a href="http://redhat.com/trusted" rel="noreferrer" target="_blank">redhat.com/trusted</a><br>
> _______________________________________________<br>
> CentOS-devel mailing list<br>
> <a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a><br>
> <a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/centos-devel</a><br>
_______________________________________________<br>
CentOS-devel mailing list<br>
<a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a><br>
<a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/centos-devel</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Branislav Náter<br>Principal Quality Engineer, Stacks QE<br>IRC: bnater at #qa #urt #brno<br>Red Hat Czech s.r.o., Purkyňova 115, 612 00, Brno, Czech Republic<br><a href="http://redhat.com" target="_blank">redhat.com</a> | TRIED. TESTED. TRUSTED. | <a href="http://redhat.com/trusted" target="_blank">redhat.com/trusted</a></div></div></div>