Closed dirkhh-cf closed 1 year ago
I think there are a few things here:
I think 1 we can tackle in the other issue, 2 seems ambitious to me at this point. I would like to see any project of ours adopt such an approach before we try and roll out out more widely. The goal is to try and write policy that mostly matches what we actually do, rather than having something aspirational that isn't followed. And we are a long way from following the second part. The first part is hopefully within reach, though.
I understand the sentiment. But I politely disagree. I think a handbook should describe what the teams should do. And I am flabergasted by the idea that a project that is used to manage "real money" would release a critical bug fix together with a breaking change.
But then again - I'm just the outside open source dude and don't work at IO - so feel free to ignore my input.
I would like to get there, I just think we should get there in smaller steps :)
Proposed starting point for the policy
Releases and their content are directly correlated to the versioning
Maintain bug fix releases for at least the last stable release, ideally for two back releases