On Tue, Jul 29, 2025 at 10:04:18AM -0700, Adam Williamson wrote: > On Tue, 2025-07-29 at 09:58 -0700, Kevin Fenzi wrote: > > On Tue, Jul 29, 2025 at 09:37:44AM +0000, Frantisek Krenzelok wrote: > > > First of all apologies for this mess. > > > I have thought this would be actually a good way to do it, unaware of the > > > full process.. > > > > > > I think we should make this at least an exemplary case and document this > > > as I have not encountered anything discouraging me from this > > > decision(that my be just me not looking at the right place..). > > > What about setting a time slot for changes like these, that they are made > > > long before the mass rebuild or right after so that we have enough time > > > to fix affected (undiscovered) packages before release > > > > I'm all for documenting this better, but where? > > > > We could perhaps add something to the reminder about the mass rebuild > > coming up (which is supposed to be a week before I think?). > > In the package update guide, maybe?
I just looked there and... not sure it fits. Thats all about making updates, but in this case you didn't even do a build. Perhaps updates policy ? We don't really have any workflow like documents for the entire thing. Where would people look for this? kevin -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to 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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
