Michel Lind kirjoitti 18.12.2024 klo
18.56:
cc-ing the packaging list - I notice the retirement process currently does not really mention any requirement to check for affected packages / to provide heads-up, which is a bit surprising since we do that (implicitly) for updating packages at least in stable releases. https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#Unretire_a_Package
Sounds like there is a gap in the process. But it is not
difficult to add a new paragraph to Policy for Orphan and Retired
Packages [1] for this.
What would be a better policy? Just say that retirement is only allowed for leaf packages, otherwise the way to get it retired is to orphan it and let that process run to its completion, whatever it might be? Or do it like API or ABI breaking updates, require one week notice on this list and directly to affected packages' maintainers?
[1]:
https://docs.fedoraproject.org/en-US/fesco/Policy_for_orphan_and_retired_packages/
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
