I would also point out that incompatible updates are still supposed to be announced a week in advance, with all impacted packages’ maintainers CC’ed or BCC’ed. This allows a week for someone to read their email and speak up about any special circumstances.
For updates with more than a handful of packages that need to be
rebuilt, making affirmative contact with a maintainer of each
package is *much* harder than just making an announcement and
saying “I’ll rebuild all of these packages unless I hear
otherwise.” I’ve never had someone ask me not to rebuild a
package, but the opportunity is there.
Note that as long as we’re on Pagure, it’s impossible to make a PR for an empty commit.
On 2/20/25 8:51 AM, Cristian Le via devel wrote:
On 2025/02/20 13:17, Miro Hrončok wrote:
What if we allowed all packagers to push empty commit to any package? That should eliminate *some* need for provenpackager access. We would also communicate in our policies that such bumps do not require prior agreement with the maintainers to avoid confusion about "what are we allowed to do".
The wording and responsibility of such power would be important. I think it would still be preferred to try an make a PR and communicate with the maintainers first to figure out if they have any plans for other changes before/after the bump. But otherwise it could be a good workaround for needing provenpackager access.
How would such a check be enforced though?
-- _______________________________________________ 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
