On Thu, Jun 12, 2025, at 15:08, Simon Tournier wrote: > For instance, if a team introduces a graft, > then this very same team must open a branch that ungrafts and then merge > this branch as soon as possible; independently of the release.
+1 We have the resources to do this and there's no reason to not be doing it. Ungrafting rarely breaks anything so it should be easy. Grafting uses energy and disk space on every user's computer. The build farm has plenty of unused capacity to ungraft, at least on x86_64, which is the only platform that seems to be widely used (there's some evidence that aarch64 has multiple users).
