On Thu, Jan 5, 2023 at 10:20 AM Michael Catanzaro <mcatanzaro@xxxxxxxxxx> wrote: > > On Wed, Jan 4 2023 at 11:46:26 PM -0500, Tom Callaway > <spotrh@xxxxxxxxx> wrote: > > Despite the size, I don't think TL updates have ever gone through > > that process before. Not opposed to doing it though, do we need to > > revert those builds from rawhide? > > Seems excessive to use the change process for "Update component to new > version." GNOME and KDE don't do that because writing a change proposal > is a bunch of extra work and there's not a ton of value from it. Cases > where we do this (e.g. Boost, python, GCC/toolchain) are more > exceptions rather than the rule, where the package maintainers think > it's especially useful to have broader coordination and awareness. That's not the reason why we don't. The reason that Fedora GNOME doesn't is because GNOME is schedule-aligned to Fedora and everything breaks at the same time anyway. The reason Fedora KDE doesn't is because we update KDE continuously. Every other desktop does generally go through the Change process. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ 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
