This document discusses Semantic Versioning (SemVer), including its major.minor.patch versioning scheme, what constitutes breaking changes, examples of how different projects implement SemVer, and alternatives to SemVer. It provides an overview of SemVer principles and challenges with implementation based on examples from projects like Kubernetes, Terraform, Ansible, MySQL, Ubuntu, MongoDB, Node.js and Linux.

1. Did Anyone Say
SemVer?
Philipp Krenn @xeraa

2. Semantic Versioning 2.0.0
https://semver.org
@xeraa

3. MAJOR.MINOR.PATCH
aka break.add.fix
@xeraa

4. Lowest and Highest Version?
1.0.0-alpha.2 1.0.0-beta 1.0.0-alpha.11
1.0.0-alpha 1.0.0-alpha.beta
@xeraa

5. THE API?
REST, client, platform — it depends
@xeraa

6. What Is Breaking?
https://xkcd.com/1172/

7. Security Fixes?
undocumented / unintended use
@xeraa

8. UI Changes?
yes or no
@xeraa

9. Before 1.0? !"
@xeraa

10. Asymmetric
add vs remove
@xeraa

11. Example: Kubernetes
replacement, deprecate, roll forward, remove
https://kubernetes.io/docs/reference/using-api/deprecation-policy/
@xeraa

12. Example: Terraform
0.x and enterprise support?
https://github.com/hashicorp/terraform/issues/15839
@xeraa

13. Example: Ansible
not SemVer but mayhem
https://www.ansible.com/blog/ansible-3.0.0-qa
@xeraa

14. Example MySQL
@xeraa

15. Example: Ubuntu
CalVer
@xeraa

16. Alternative
MongoDB < 5.0
node.js < 1.0
Linux 1.0 – 2.6.x

17. Did Anyone Say
SemVer?
Philipp Krenn @xeraa