On Sat, Mar 25, 2023 at 12:51 PM Miro Hrončok <mhroncok@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.