[9659]

Just because it can be measured, doesn't mean it should be.

These 'measures' would be much more useful if they were used to determine the control limits of the software process being used.

'hours from pull request to merge' for an open source project is silly. who cares? 'number of commits a month'? who cares. what is the value of those commits.

why the focus on 'constant churn of software'? I don't see it.

[jayantbhawal]

I get where you're coming from, and can see a lot of people seeing it that way.

But to me, metrics like 'PR to merge time' help highlight bottlenecks, even in open source. It’s not just about churn, it’s about ensuring contributions are flowing smoothly. Quality matters, but so does making sure contributions don’t stall.