The change has now been implemented.
We'll have to wait for a package to be affected before we see it, but I
*think* it should look like what we have there.
Note: It is still doing everything as separate steps. So package
maintainers will still get several emails.
I got to see the code, and I think we can trim a couple of the steps off,
which will trim a couple of the emails off.
But I wanted to get this change through first, because it's a
straightforward wording change and shouldn't break anything.
Troy
On Fri, Mar 31, 2023 at 8:00 AM Carl George <carl(a)redhat.com> wrote:
That sounds great, thanks.
On Thu, Mar 30, 2023, 8:28 AM Troy Dawson <tdawson(a)redhat.com> wrote:
> It doesn't look like they've done their merge yet, so I'll see if I can
> get your change in.
> How does this sound?
>
> Subject:
> Notice: <package> will be automatically retired from EPEL <major> when
> RHEL <major>.<minor> is released
>
> Comment:
>
> This issue is purely informational, you do not need to take any action.
> Thank you for your work maintaining <package> in EPEL <major>. Red Hat
> considers this package important enough to promote it to official RHEL. It
> will be part of RHEL <major>.<minor>. Please do not update
<package> in
> EPEL <major> so the RHEL version can have a higher version and release.
> When RHEL <major>.<minor> is released, EPEL automation will remove
> <package> from EPEL <major> and close this bug.
>
>
> On Tue, Mar 28, 2023 at 9:14 AM Carl George <carl(a)redhat.com> wrote:
>
>> I'm also late to the party with this feedback, but just in case it's
>> not too late to include, can we include something about not updating
>> the package further? Beyond just "you do not need to take any
>> action", we should advise against making any changes at that point, as
>> often the RHEL package will be exactly one release higher than the
>> current EPEL package, and updating the EPEL package further (either
>> release or version) will screw up the upgrade path.
>>
>> On Mon, Mar 27, 2023 at 7:22 PM Troy Dawson <tdawson(a)redhat.com> wrote:
>> >
>> > On Sat, Mar 25, 2023 at 12:51 PM Miro Hrončok <mhroncok(a)redhat.com>
>> wrote:
>> >>
>> >> On 20. 03. 23 12:20, Neal Gompa wrote:
>> >> >> I could think of other reasons as well. E.g. it's not
important
>> for customers
>> >> >> but it's important for Red Hat. Or maybe it is a
not-so-important
>> dependency of
>> >> >> something else.
>> >> >>
>> >> > Does Red Hat have any other motivation with RHEL other than a
>> customer
>> >> > needing the functionality? Those other reasons are generally
driven
>> by
>> >> > someone needing it.
>> >>
>> >> See e.g.
https://bugzilla.redhat.com/2175213
>> >
>> >
>> > I see your point. It sometimes also happens when the EPEL package is
>> a dependency of the important package, the customers aren't actually asking
>> for the EPEL package.
>> > It looks like this change still hasn't been merged in so I'll see if
I
>> can get a change in. How about this?
>> >
>> > Subject:
>> > Notice: <package> will be automatically retired from EPEL
<major> when
>> RHEL <major>.<minor> is released
>> >
>> > Comment:
>> >
>> > This issue is purely informational, you do not need to take any
>> action. Thank you for your work maintaining <package> in EPEL
<major>.
>> Red Hat considers this package important enough to promote it to official
>> RHEL. It will be part of RHEL <major>.<minor>. When that is
released,
>> EPEL automation will remove <package> from EPEL <major> and close
this bug.
>> >
>> > _______________________________________________
>> > 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/epel-devel@lists.fedoraproj...
>> > Do not reply to spam, report it:
>>
https://pagure.io/fedora-infrastructure/new_issue
>>
>>
>>
>> --
>> Carl George
>> _______________________________________________
>> 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/epel-devel@lists.fedoraproj...
>> Do not reply to spam, report it:
>>
https://pagure.io/fedora-infrastructure/new_issue
>>
> _______________________________________________
> 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/epel-devel@lists.fedoraproj...
> Do not reply to spam, report it:
>
https://pagure.io/fedora-infrastructure/new_issue
>
_______________________________________________
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/epel-devel@lists.fedoraproj...
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue