|
|
|
|
|
by vorpalhex
2688 days ago
|
|
It's easy to treat all things in programming as if they're algorithms, but we should remember that there's people behind them too. As a maintainer, it's on you to communicate effectively to your users. If you're patching buggy behavior but it's likely to break code, then a major bump may be appropriate. Likewise if your refactor is massively changing your basic contracts, then it may be wise to fork your own work and move to a new repo and name. Semvers value is that it offers a clear enough guideline most of the time, which is about the best we can ask for. |
|