On Thu, Mar 16, 2023 at 3:43 PM Kevin Fenzi <ke...@scrye.com> wrote:
> On Thu, Mar 16, 2023 at 03:10:23PM -0700, Troy Dawson wrote: > > > > This is what I have on my ticket. Respond soon (by tomorrow end of day) > if > > you think I need changes. > > > > Subject: > > Notice: <package> will be automatically retired from epel<major> when > RHEL > > <major>.<minor> is released > > > > Comment: > > Thank you for your work maintaining <package> in epel<major>. This > package > > has been considered important enough to Red Hat's customers that Red Hat > > has decided to promote it to be an official part of RHEL. It will be > part > > of RHEL <major>.<minor>. When that is released, EPEL automation will > > remove <package> from epel<major>. > > That looks pretty good, but I might suggest adding something more > explicit at the end: > > Note that this issue is purely informational, you do not need to take any > actions at this time. > > But perhaps thats overkill. ;) > > kevin > It's slight overkill, but you are correct, they might think they have to do something. I have changed the last sentence to be When that is released, EPEL automation will remove <package> from EPEL <major> and close this bug. Troy
_______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue