-
-
Notifications
You must be signed in to change notification settings - Fork 398
Add alpha to version #1052
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
Add alpha to version #1052
Conversation
what about adding a field like |
Right! Didn't think about the JSON output. |
@cmaglie @silvanocerza |
5cd397e
to
af32a06
Compare
What do you think about programmatically interpreting
It's mostly the stable pre-release where I think this would be important, because it would be strange to mark a pre-release as "stable". So not necessarily something to do right now, but maybe worth considering. Ideally, there would be a different status for the nightly/test builds. |
What semver will indicate the Beta state? |
AFAIK, there is no concept of alpha/beta in semver. There is only unstable (0.y.z) and stable. So the switch from alpha to beta would just be a matter of manually changing the string whenever that point is deemed to have been reached. With the multi-word status approach, the switch from "beta" to "stable" would only happen once, so that might as well be done manually as well. It's with the non-release versions that the programmatical status determination becomes useful, since it would not make sense to do that manually. |
Actually there is, see this: https://semver.org/#spec-item-9 |
Please check if the PR fulfills these requirements
before creating one)
our contributing guidelines
Updates
version
command.Alpha is not specified when printing version.
Calling
version
command specifies that we're in alpha.Example:
arduino-cli alpha Version: 0.0.0-git Commit: 83abde23
No.
None.
See how to contribute