Semantic Versioning?

[fabianegli]

I was unable to find a commitment to a specific versioning scheme. Wouldn't it make sense to commit to one so other tools know what to expect? e.g. https://github.com/fabianegli/proteomicslfq/blob/dev/bin/scrape_software_versions.py tries to extract the version with too simple a regex. Committing to a versioning scheme would allow to use a regex that is guaranteed to work.

This would not need any code change, but an addition to the documentation:

• documentation about how to create a release
• a note in the README about the versioning scheme being followed (that could be a badge, too)
• Mentioning it here: https://github.com/OpenMS/OpenMS/wiki#-development-model

[timosachsenberg]

good point we will bring this up on our regulr developer meetings

[tapaswenipathak]

What is the documentation todo? Should this be closed?

[jpfeuffer]

We should document on how we version. I.e. what a minor version increase means for us. We are currently not strictly sticking to semantic versioning. It is tricky while our tools and library are versioned together.