EffVer

Transcript

1. 2.4.8
2. 2.4.8 2.5.0
3. 2.5.0 Semantic Versioning (SemVer) MAJOR incompatible API changes MINOR Backward compatible features PATCH backward compatible bug fixes https://semver.org/
4. Hyrum’s Law Further reading https://xkcd.com/1172/ https://www.hyrumslaw.com/ https://hynek.me/articles/semver-will-not-save-you/ With a sufficient number of users of an API, it does not matter what you promise in the contract: all observable behaviors of your system will be depended on by somebody.
5. 2024.7.8
6. 2024.7.8 2024.8.0
7. 2024.8.0 Calendar Versioning (CalVer) YEAR year of release MONTH month of release INCREMENT Monotonic index (allows multiple releases in a day) https://calver.org/
8. https://jacobtomlinson.dev/posts/2023/sometimes-i-regret-using-calver/
9. https://jacobtomlinson.dev/posts/2023/sometimes-i-regret-using-calver/
10. Is there another way?
11. Is there another way? Many Python projects already do things differently, let’s give it a name!
12. EffVer Used by And likely many more… jacobtomlinson.dev/effver
13. Macro Meso Micro Upgrading to a new version intends to require: no effort some effort a large effort EffVe jacobtomlinson.dev/effver
14. 2.4.8 2.5.0
15. Benefits of EffVer • EffVer communicates intentions to busy humans writing software • EffVer respects that all releases require effort from downstream developers • Users can more easily decide when to read the CHANGELOG of an EffVer project • EffVer doesn’t differentiate between features and bugs, only impacts • EffVer helps you fix “broken” releases where the wrong version was chosen • EffVer lets you develop with a 0.x.x version that contains useful information jacobtomlinson.dev/effver