Proposal to Standardize Release Tagging Using Semantic Versioning

Description

Dear Gittyup Developers,

I have noticed an inconsistency in the version tagging within the releases section that could potentially confuse users trying to track changes or understand the progression of releases.

Examples of Current Version Tagging

Here are a few examples from the Releases page that illustrate the current inconsistency in version naming:

• development Gittyup-1.4.0-dev.dmg
• gittyup_v1.4.0 Gittyup-1.4.0.dmg
• latest Gittyup-1.2.0-dev.dmg
• stable Gittyup-1.2.2.dmg

I don't understand why 1.4.0-dev comes before 1.4.0.

Suggestion

I noticed that the file download list already follows SemVer, but the tree/tag does not follow SemVer.I recommend standardizing the version numbering format by adopting Semantic Versioning (SemVer):

• 1.4.0-dev
• 1.4.0-alpha.1
• 1.4.0-beta.1
• 1.4.0-rc.1
• 1.4.0

Conclusion

I hope you will consider this proposal to standardize version numbering. I believe adopting SemVer can significantly streamline development workflows and help both contributors and users to better understand the significance of each release.

Thank you for considering this suggestion, and for your continued work on this valuable project.

Start with the GitHub Releases page and compare the development, latest, stable, and gittyup_v1.4.0 tags with their downloadable filenames. Read the Semantic Versioning guidance linked in the issue and inspect the project’s release process to identify where tag names are produced. Done means the release tags and artifacts follow one consistent, documented version sequence.