Skip to content

Decide on versioning scheme #8

Closed

Description

@BenjaminRodenberg

We could use Semantic Versioning: https://semver.org/

Since this is not a library but a command line application a simpler scheme might also be appropriate.

Activity

  1. BenjaminRodenberg commented on Nov 11, 2025

    @BenjaminRodenberg
    CollaboratorAuthor

    The main alternative to semantic versioning is a calendar-based system. See here.

    I would prefer a Semantic Versioning because:

    • We can communicate with the 0.*.* release cycle we can communicate that the API is not yet stable. Since this project is quite new I expect that we will spend some time in this unstable phase before we enter the 1.*.* release cycle.
    • I have more experience with Semantic Versioning
  2. BenjaminRodenberg commented on Nov 13, 2025

    @BenjaminRodenberg
    CollaboratorAuthor

    In #31 I'm relying on semantic versioning. I would suggest to keep it at this if nobody objects.

  3. wardvp commented on Nov 18, 2025

    @wardvp
    Collaborator

    The semantic versioning is fine with me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

usabilityImproves the user experience

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions