Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

If even the tiniest backwards incompatible changes to the public API require a major version bump, won I end up at version 42.0.0 very rapidly?

April 26, 2017API backwards bump changes incompatible public require tiniest version

0

Posted

If even the tiniest backwards incompatible changes to the public API require a major version bump, won I end up at version 42.0.0 very rapidly?

1 Answer

0

Posted

This is a question of responsible development and foresight. Incompatible changes should not be introduced lightly to software that has a lot of dependent code. The cost that must be incurred to upgrade can be significant. Having to bump major versions to release incompatible changes means you’ll think through the impact of your changes, and evaluate the cost/benefit ratio involved.