Skip to content

Use semver for your version numbers #4135

@hoall

Description

@hoall

First of all, thank you for your awesome work. I love your tool and use it in private as well as at work.

I am most of the time confused when you release a new version of keepassXC.

Like the current release 2.5.2 you did a lot of changes. You did:

  • add new functionality
  • adaptions
  • and bugfixes

Although your version number only changed in the third position, indicating (at least in my eyes) just bugfixes, even though you did much more.

To honor your work more in the version number, I suggest to use semver . Semver is a simple versioning scheme using three positions. Basically the first one is for breaking changes in the API, the second for additional functionality and bugfixes included, and the third for pure bugfixes.

I use KeepassXC now for a while and I would say you could be by version 2.10 or more. I know it is just versioning, but:

  • it would honor your work much more in my opinion
  • most people would know instantly if it is a release with breaking changes, new functions or bugfixes.

So, it's just a small wish, nothing mandatory, but maybe it would also remove the headache from the developer thinking about which would be the next version number :)

Best Regards

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions