We fail to follow SemVer – and why it needn't matter

https://skillsmatter.com/conferences/6612-fullstack#program

1. 125,000 @boennemann packages on npm
2. @boennemann 200,00 packages on npm
3. Each package is a problem solved @boennemann
4. @boennemann
5. 1. npmsearch.com @boennemann
6. 1. npmsearch.com 2. npm install <package> @boennemann
7. 1. npmsearch.com 2. npm install <package> 3. ? @boennemann
8. 1. npmsearch.com 2. npm install <package> 3. ? 4. profit @boennemann
9. X.Y.Z @boennemann
10. X.Y.Z @boennemann Major Minor Patch http://semver.org
11. @boennemann Major Minor Patch http://semver.org 1.0.0
12. @boennemann Major Minor Patch http://semver.org 1.0.1
13. @boennemann Major Minor Patch http://semver.org 1.1.0
14. @boennemann Major Minor Patch http://semver.org 2.0.0
15. 2.0.0 @boennemann Major Minor Patch
16. 2.0.0 @boennemann Major Minor Patch
17. 2.0.0 @boennemann Patch Breaking Feature
18. 2.0.0 @boennemann Breaking Feature Patch http://semver.npmjs.com/
19. 2.0.0 @boennemann Breaking Feature Patch http://semver.npmjs.com/ ~
20. 2.0.0 @boennemann Breaking Feature Patch http://semver.npmjs.com/ ^
21. not really @boennemann
22. We fail to follow SemVer @boennemann
23. @boennemann http://npmbynumbers.bocoup.com/
24. @boennemann http://npmbynumbers.bocoup.com/ 0.y.z >0.y.z
25. Anything may change at any time @boennemann
26. @boennemann
27. No changelogs @boennemann
28. @boennemann
29. @boennemann
30. @boennemann
31. Hauptversionsnummern- erhöhungsangst¹ @boennemann ¹ Fear of increasing the major version
32. If we strictly followed “semantic” versioning, it would probably be Backbone.js 43.0.0 by now — which doesn't help anyone evaluate the actual progress of the project. – Jeremy Ashkenas, http://backbonejs.org/ @boennemann
33. evaluate the actual progress of the project @boennemann
34. @boennemann
35. Versions are not for humans @boennemann
36. @boennemann
37. @boennemann
38. @boennemann 1.x 2.x
39. @boennemann 1.x 1.x
40. Versions are not for humans – names are @boennemann
41. @boennemann – Stephan Seidt, http://fucking.engineering/
42. Our tools are so bad, we value human readability in computer protocols when it really doesn’t. fucking. matter. @boennemann – Stephan Seidt, http://fucking.engineering/
43. We fail to follow SemVer and why it needn’t matter @boennemann
44. we need better tools @boennemann
45. semantic-release fully automated package publishing @boennemann
46. @boennemann
47. @boennemann – http://egghead.io/
48. Trust us, this will change your workflow for the better @boennemann – http://egghead.io/
49. ⭐⭐⭐ git.io/semantic-release @boennemann
50. @boennemann
51. automated dependency updates and testing @boennemann
52. @boennemann
53. @boennemann
54. @boennemann
55. npm install -g greenkeeper http://greenkeeper.io @boennemann
56. @boennemann
57. @boennemann
58. Thank you @boennemann