Upgrade to Pro — share decks privately, control downloads, hide ads and more …

On the Meaning of Version Numbers

Hynek Schlawack
April 25, 2020
290

On the Meaning of Version Numbers

Hynek Schlawack

April 25, 2020
Tweet

Transcript

  1. Very few open source projects have the resources to maintain

    more than one release branch (properly). “I can choose to only get bugfixes.” @hynek
  2. -No security updates. -The longer you wait, the harder it

    gets. If You Pin Major Version In Your Applications @hyne
  3. @hynek If You Pin Major Version In Your Public Package

    your-pkg urllib3 1.25.9 User’s App
  4. @hynek If You Pin Major Version In Your Public Package

    your-pkg urllib3 1.25.9 User’s App <2.0
  5. @hynek If You Pin Major Version In Your Public Package

    your-pkg urllib3 1.25.9 User’s App <2.0 2.0.0
  6. @hynek If You Pin Major Version In Your Public Package

    your-pkg urllib3 1.25.9 User’s App <2.0 other- pkg >2.0 2.0.0
  7. @hynek If You Pin Major Version In Your Public Package

    your-pkg urllib3 1.25.9 User’s App <2.0 other- pkg >2.0 Conflict! 2.0.0
  8. 1. Have tests. 2. Pin your dependencies. 3. Try to

    update dependencies. 4. See if tests still pass. @hynek
  9. 1. Have tests. 2. Pin your dependencies. 3. Try to

    update dependencies. 4. See if tests still pass. 5. GOTO 3 @hynek
  10. A concept that most people get wrong is not a

    useful concept for most people. @hynek
  11. Takeaways •Don’t believe the promises of SemVer. •Don’t do SemVer

    if you’re afraid to increment major. •Try CalVer! @hynek