Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could you please explain your version number convention? #160

Open
chrbertsch opened this issue Feb 24, 2025 · 3 comments
Open

Could you please explain your version number convention? #160

chrbertsch opened this issue Feb 24, 2025 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@chrbertsch
Copy link

Until version 2.4.1. you seem to have followed semantic versioning.
Then you introduced an "a" in your version numbers, e.g. "3.0a5". What does this mean? Is this explained somewhere?
Thanks in advance for clarifying.

@chrbertsch chrbertsch added the enhancement New feature or request label Feb 24, 2025
@modelonrobinandersson
Copy link
Member

Hi @chrbertsch!
The "a" is to indicate an "alpha" release. In the future you will likely also see a "3.0b1" which would a beta release, or to be exact "the first beta release of 3.0".
Let me know if you have any more questions, happy to help!

@modelonrobinandersson modelonrobinandersson self-assigned this Feb 24, 2025
@chrbertsch
Copy link
Author

Ah, thanks.
Could you explain this in the "Relesae notes" and write the "alpha" explicitly as suggested in semantic versioning https://semver.org/?
And perhaps call the "release" of an alpha version "prerelease" in Github, see e.g. how we do it for the FMI Standard https://github.com/modelica/fmi-standard/releas

@modelonrobinandersson
Copy link
Member

@chrbertsch sure no problem, I have clarified your request in the release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants