Re: EPEL2RHEL - New Wording? - New Workflow?

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

 



On 01. 09. 22 0:19, Troy Dawson wrote:
** Solution(s)
A - At the very least, we need to change the wording of the bugs.  I am proposing the following

Subject: Remove <package> from epel9 when rhel 9.1 is released
Comment: This package is being added to RHEL 9.1 at the next minor release. After the next RHEL minor release, please verify this package was released in RHEL, and if so remove it from epel9.

Yes please. Ideally, even add a reproducer that verifies this ("go to X and search for the package name" or "run this repoquery" or even "go to this documentation page to check it")

B - If possible, move the EPEL2RHEL check to later in the development cycle.  I would like it to be in the step where the packages get added to BaseOS, AppStream, or CRB.  That way we would know it isn't going to be a BuildRoot only package, and it would reduce the time the bugs sit waiting.
I don't know if this is possible, but I'm going to ask.

Agreed. It could even say which (sub)packages are being added and link to the appropriate documentation in case some of the EPEL subpackages need to be split into a spearate component.

C - ?? What if we only created the bugs on the tracker itself, and not the individual packages ??
Would that be a good thing?  Or would it irritate the maintainers?

What do you mean by this? I don't understand it. File it against the distribution? If there is a dedicated (and educated) person/team who would deal with this at all RHEL release boundaries, than this makes sense. Otherwise it just hides this information from the EPEL maintainers.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
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