Yeah I'm not defending that. I think it's another constraint of continuous delivery and cooperative development. The more people work on a project, the less breaking changes can be introduced by design of git branches, they must converge. Now in practice I'm sure this is actually different, I'm making an assumption here. I breaking changes are difficult to cooperate, and maintain a productive cadence among teams, it's frustrating as well. oss guys have even harder times prioritizing contributors too. It means more work for project leads as well, resolving merge conflicts all day. So again I think it's the leaky abstraction from attempting to maintain smooth dev cooperation with a stable release cadence. I can say it's generally not from retardation lol. If a bug was known, but the patch not released, there was likely a cooperative reason imo. That's also to say dev pipelines are pretty deep too. I mean PMs have to schedule merging of PRs, that bugfix likely wouldn't converge in time with the staged PRs so it gets pushed back.