3 ms·
I don't buy that the need to bump Major is a failure. This is particularly true if you continue to maintain the previous major version to the same degree (if a
by tialaramex 5y ago
I don't buy that the need to bump Major is a failure.
This is particularly true if you continue to maintain the previous major version to the same degree (if any) that you maintain the new one, and especially true if you have an explicit release lifetime strategy.
If I tell you that misfortunate 1.x will be actively seeing new work until 2025 and then bug fixes until 2028, and I deliver, misfortunate 2.x doesn't break that promise. Maybe you wish a new feature from misfortunate 2.6 could have been in 1.34 instead, but too bad I never promised that and most likely the way I did it would be incompatible with 1.34 anyway.
I also think that people underestimate how bad bugs can be. Sometimes the minimum fix is a breaking change.