home.social

#semanticversioning — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #semanticversioning, aggregated by home.social.

  1. The failure of #SemanticVersioning is that, once a project/library reaches some degree of mature popularity, nobody ever wants to bump the first digit. They'll find endless excuses not to.

    So if your project got really established at version 1.1, it'll be version 1.something forever.

    Like many geeky technical things, SV's an elegant solution that completely fails to account for how people behave.

  2. The failure of #SemanticVersioning is that, once a project/library reaches some degree of mature popularity, nobody ever wants to bump the first digit. They'll find endless excuses not to.

    So if your project got really established at version 1.1, it'll be version 1.something forever.

    Like many geeky technical things, SV's an elegant solution that completely fails to account for how people behave.

  3. The failure of #SemanticVersioning is that, once a project/library reaches some degree of mature popularity, nobody ever wants to bump the first digit. They'll find endless excuses not to.

    So if your project got really established at version 1.1, it'll be version 1.something forever.

    Like many geeky technical things, SV's an elegant solution that completely fails to account for how people behave.

  4. The failure of #SemanticVersioning is that, once a project/library reaches some degree of mature popularity, nobody ever wants to bump the first digit. They'll find endless excuses not to.

    So if your project got really established at version 1.1, it'll be version 1.something forever.

    Like many geeky technical things, SV's an elegant solution that completely fails to account for how people behave.

  5. The failure of #SemanticVersioning is that, once a project/library reaches some degree of mature popularity, nobody ever wants to bump the first digit. They'll find endless excuses not to.

    So if your project got really established at version 1.1, it'll be version 1.something forever.

    Like many geeky technical things, SV's an elegant solution that completely fails to account for how people behave.

  6. 📰 bump というバージョンバンプツールを作った (👍 35)

    🇬🇧 Created 'bump': a universal version bumping tool supporting multiple languages (Go, Rust, Python, etc.) with semantic versioning. Inspired by gobump.
    🇰🇷 'bump' 개발: Go, Rust, Python 등 여러 언어를 지원하는 범용 버전 범핑 도구. 시맨틱 버저닝 적용. gobump에서 영감을 받음.

    🔗 zenn.dev/mattn/articles/28ff86

    #DevTools #SemanticVersioning #CLI #Zenn

  7. 📰 bump というバージョンバンプツールを作った (👍 35)

    🇬🇧 Created 'bump': a universal version bumping tool supporting multiple languages (Go, Rust, Python, etc.) with semantic versioning. Inspired by gobump.
    🇰🇷 'bump' 개발: Go, Rust, Python 등 여러 언어를 지원하는 범용 버전 범핑 도구. 시맨틱 버저닝 적용. gobump에서 영감을 받음.

    🔗 zenn.dev/mattn/articles/28ff86

    #DevTools #SemanticVersioning #CLI #Zenn

  8. 📰 bump というバージョンバンプツールを作った (👍 35)

    🇬🇧 Created 'bump': a universal version bumping tool supporting multiple languages (Go, Rust, Python, etc.) with semantic versioning. Inspired by gobump.
    🇰🇷 'bump' 개발: Go, Rust, Python 등 여러 언어를 지원하는 범용 버전 범핑 도구. 시맨틱 버저닝 적용. gobump에서 영감을 받음.

    🔗 zenn.dev/mattn/articles/28ff86

    #DevTools #SemanticVersioning #CLI #Zenn

  9. 📰 bump というバージョンバンプツールを作った (👍 35)

    🇬🇧 Created 'bump': a universal version bumping tool supporting multiple languages (Go, Rust, Python, etc.) with semantic versioning. Inspired by gobump.
    🇰🇷 'bump' 개발: Go, Rust, Python 등 여러 언어를 지원하는 범용 버전 범핑 도구. 시맨틱 버저닝 적용. gobump에서 영감을 받음.

    🔗 zenn.dev/mattn/articles/28ff86

    #DevTools #SemanticVersioning #CLI #Zenn

  10. 📰 bump というバージョンバンプツールを作った (👍 35)

    🇬🇧 Created 'bump': a universal version bumping tool supporting multiple languages (Go, Rust, Python, etc.) with semantic versioning. Inspired by gobump.
    🇰🇷 'bump' 개발: Go, Rust, Python 등 여러 언어를 지원하는 범용 버전 범핑 도구. 시맨틱 버저닝 적용. gobump에서 영감을 받음.

    🔗 zenn.dev/mattn/articles/28ff86

    #DevTools #SemanticVersioning #CLI #Zenn

  11. One of the things that #EmberJS & it's ecosystem does (mostly) correctly wrt/ #SemanticVersioning is:

    ✅ Major versions are for breaking changes.
    ❌ Major versions are for adding fancy new features.

    It looks weird and less shiny at first, but let me reassure you: Once you start maintaining any slightly more complicated codebase, this is an absolute blessing.

  12. One of the things that #EmberJS & it's ecosystem does (mostly) correctly wrt/ #SemanticVersioning is:

    ✅ Major versions are for breaking changes.
    ❌ Major versions are for adding fancy new features.

    It looks weird and less shiny at first, but let me reassure you: Once you start maintaining any slightly more complicated codebase, this is an absolute blessing.

  13. One of the things that #EmberJS & it's ecosystem does (mostly) correctly wrt/ #SemanticVersioning is:

    ✅ Major versions are for breaking changes.
    ❌ Major versions are for adding fancy new features.

    It looks weird and less shiny at first, but let me reassure you: Once you start maintaining any slightly more complicated codebase, this is an absolute blessing.

  14. One of the things that #EmberJS & it's ecosystem does (mostly) correctly wrt/ #SemanticVersioning is:

    ✅ Major versions are for breaking changes.
    ❌ Major versions are for adding fancy new features.

    It looks weird and less shiny at first, but let me reassure you: Once you start maintaining any slightly more complicated codebase, this is an absolute blessing.

  15. One of the things that #EmberJS & it's ecosystem does (mostly) correctly wrt/ #SemanticVersioning is:

    ✅ Major versions are for breaking changes.
    ❌ Major versions are for adding fancy new features.

    It looks weird and less shiny at first, but let me reassure you: Once you start maintaining any slightly more complicated codebase, this is an absolute blessing.

  16. Une proposition intéressante d'ajouter une notion supplémentaire au *Semantic Versioning* pour distinguer les "simples" breaking changes des changements plus conséquents.

    L'intérêt de cette approche est qu'elle reste compatible avec le semantic versionning lui-même.

    🔗 antfu.me/posts/epoch-semver

    #version #SemanticVersioning

  17. Une proposition intéressante d'ajouter une notion supplémentaire au *Semantic Versioning* pour distinguer les "simples" breaking changes des changements plus conséquents.

    L'intérêt de cette approche est qu'elle reste compatible avec le semantic versionning lui-même.

    🔗 antfu.me/posts/epoch-semver

    #version #SemanticVersioning

  18. Une proposition intéressante d'ajouter une notion supplémentaire au *Semantic Versioning* pour distinguer les "simples" breaking changes des changements plus conséquents.

    L'intérêt de cette approche est qu'elle reste compatible avec le semantic versionning lui-même.

    🔗 antfu.me/posts/epoch-semver

    #version #SemanticVersioning

  19. Convention over customization.
    This is why I love projects like Keep a Changelog, Conventional Commits and Semantic Versioning. They allow for some neat processing by other tools which just wouldn't ever be possible if everyone did their own, custom thing.

    #git #ConventionalCommits #SemanticVersioning #Neovim #NeovimLazy

  20. Convention over customization.
    This is why I love projects like Keep a Changelog, Conventional Commits and Semantic Versioning. They allow for some neat processing by other tools which just wouldn't ever be possible if everyone did their own, custom thing.

  21. Convention over customization.
    This is why I love projects like Keep a Changelog, Conventional Commits and Semantic Versioning. They allow for some neat processing by other tools which just wouldn't ever be possible if everyone did their own, custom thing.

    #git #ConventionalCommits #SemanticVersioning #Neovim #NeovimLazy

  22. Convention over customization.
    This is why I love projects like Keep a Changelog, Conventional Commits and Semantic Versioning. They allow for some neat processing by other tools which just wouldn't ever be possible if everyone did their own, custom thing.

    #git #ConventionalCommits #SemanticVersioning #Neovim #NeovimLazy

  23. Convention over customization.
    This is why I love projects like Keep a Changelog, Conventional Commits and Semantic Versioning. They allow for some neat processing by other tools which just wouldn't ever be possible if everyone did their own, custom thing.

    #git #ConventionalCommits #SemanticVersioning #Neovim #NeovimLazy