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

2022-05-20 Thread Josh Boyer 
On Fri, May 20, 2022 at 1:42 AM Thomas Stephen Lee  wrote:
>
> The package I need is redhat-lsb-core.

We have no plans to add redhat-lsb-core at this time.  Most users are
able to port their software to use the fields in /etc/os-release.

josh

> On Fri, May 20, 2022 at 1:57 AM Josh Boyer  wrote:
> >
> > On Thu, May 19, 2022 at 4:11 PM Kevin Fenzi  wrote:
> > >
> > > On Thu, May 19, 2022 at 07:37:46AM +0200, Branislav Náter wrote:
> > > > Hi,
> > > >
> > > > On Thu, May 19, 2022 at 4:15 AM Thomas Stephen Lee 
> > > > 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.
> > >
> > > Please don't file it there. :)
> >
> > Small point of clarification.  If you want to add a package to Red Hat
> > Enterprise Linux 9 (the product), then you should likely open a
> > support case via the Customer Portal and request it as an RFE.
> >
> > If you want to request a subpackage of an existing RHEL 9 package that
> > is not included in RHEL, follow this and replace 8 with 9:
> > https://wiki.centos.org/FAQ/CentOS8/UnshippedPackages
> >
> > If you want to add a package to Extra Packages for Enterprise Linux 9
> > (the wonderful community project), then follow what Kevin says below.
> >
> > It really depends on the exact thing you are after.
> >
> > josh
> >
> >
> > > Take a look at the handy doc:
> > >
> > > https://docs.fedoraproject.org/en-US/epel/epel-package-request/
> > >
> > > If anything is unclear there, please do let us know.
> > >
> > > While RHEL may be moving to jira with RHEL10, EPEL is very likely to
> > > stay with whatever Fedora is using (currently bugzilla).
> > >
> > > kevin
> > > ___
> > > CentOS-devel mailing list
> > > centos-de...@centos.org
> > > https://lists.centos.org/mailman/listinfo/centos-devel
> >
> > ___
> > CentOS-devel mailing list
> > centos-de...@centos.org
> > https://lists.centos.org/mailman/listinfo/centos-devel
> ___
> CentOS-devel mailing list
> centos-de...@centos.org
> https://lists.centos.org/mailman/listinfo/centos-devel
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@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

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

2022-05-19 Thread Josh Boyer 
On Thu, May 19, 2022 at 4:11 PM Kevin Fenzi  wrote:
>
> On Thu, May 19, 2022 at 07:37:46AM +0200, Branislav Náter wrote:
> > Hi,
> >
> > On Thu, May 19, 2022 at 4:15 AM Thomas Stephen Lee 
> > 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.
>
> Please don't file it there. :)

Small point of clarification.  If you want to add a package to Red Hat
Enterprise Linux 9 (the product), then you should likely open a
support case via the Customer Portal and request it as an RFE.

If you want to request a subpackage of an existing RHEL 9 package that
is not included in RHEL, follow this and replace 8 with 9:
https://wiki.centos.org/FAQ/CentOS8/UnshippedPackages

If you want to add a package to Extra Packages for Enterprise Linux 9
(the wonderful community project), then follow what Kevin says below.

It really depends on the exact thing you are after.

josh


> Take a look at the handy doc:
>
> https://docs.fedoraproject.org/en-US/epel/epel-package-request/
>
> If anything is unclear there, please do let us know.
>
> While RHEL may be moving to jira with RHEL10, EPEL is very likely to
> stay with whatever Fedora is using (currently bugzilla).
>
> kevin
> ___
> CentOS-devel mailing list
> centos-de...@centos.org
> https://lists.centos.org/mailman/listinfo/centos-devel
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@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

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

2022-05-19 Thread Kevin Fenzi 
On Thu, May 19, 2022 at 07:37:46AM +0200, Branislav Náter wrote:
> Hi,
> 
> On Thu, May 19, 2022 at 4:15 AM Thomas Stephen Lee 
> 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.

Please don't file it there. :) 

Take a look at the handy doc: 

https://docs.fedoraproject.org/en-US/epel/epel-package-request/

If anything is unclear there, please do let us know. 

While RHEL may be moving to jira with RHEL10, EPEL is very likely to
stay with whatever Fedora is using (currently bugzilla). 

kevin


signature.asc
Description: PGP signature
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@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

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

2022-05-19 Thread Thomas Stephen Lee 
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  wrote:
>
> Hi,
>
> On Thu, May 19, 2022 at 4:15 AM Thomas Stephen Lee  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  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-le...@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-de...@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-de...@centos.org
> https://lists.centos.org/mailman/listinfo/centos-devel
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@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

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

2022-03-11 Thread 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
> ?  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 -- de...@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@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/de...@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@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

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

2022-03-11 Thread 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
?  From the looks of it, it probably should
just be switched off?

Thanks,
Florian
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@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

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

2022-03-10 Thread Josh Boyer 
On Wed, Mar 9, 2022 at 5:05 PM Davide Cavalca via CentOS-devel
 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
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@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