Re: EPEL2RHEL - New Wording? - New Workflow?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Mar 16, 2023 at 6:10 PM Troy Dawson <tdawson@xxxxxxxxxx> wrote:
>
> On Mon, Feb 20, 2023 at 6:33 AM Troy Dawson <tdawson@xxxxxxxxxx> wrote:
>>
>>
>>
>> On Sun, Feb 19, 2023 at 6:25 PM Gary Buhrmaster <gary.buhrmaster@xxxxxxxxx> wrote:
>>>
>>> On Mon, Sep 5, 2022 at 9:33 AM Dominik 'Rathann' Mierzejewski
>>> <dominik@xxxxxxxxxxxxxx> wrote:
>>>
>>> > It would be really nice if the wording of the bug could contain some
>>> > kind of a "thank you" note to the EPEL maintainers of the package in
>>> > question. Not everyone will understand this process as "great, I don't
>>> > have to maintain package X anymore, Red Hat will be doing that for me
>>> > from now on". Some folks may take it as "Oh no! Red Hat is taking away
>>> > my toy! Why?!" Ideally, there should still be a way for EPEL
>>> > maintainer(s) to continue contributing to the RHEL package.
>>>
>>> Perhaps add something like (wordsmithed by someone
>>> competent in such things):
>>>
>>> "The package you have been maintaining in EPEL is now
>>> considered important enough to a large enough part of our
>>> customers that Red Hat has decided to promote it to being
>>> an officially supported part of the product...."
>>
>>
>> I like that idea.  It's much more positive.  A nice "Thank you for doing this in EPEL" type of feel.
>>
>> Troy
>
>
> 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 is pretty well worded, though you can just use "EPEL <major>"
instead of "epel<major>".



-- 
真実はいつも一つ!/ Always, there's only one truth!
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux