New release 0.4.0-alpha #638
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
Ph0enixKM
requested review from
Mte90,
CymDeveloppement,
hdwalters,
mks-h,
b1ek and
KrosFire
mks-h
approved these changes
Dec 18, 2024
hdwalters
approved these changes
Dec 19, 2024
There was a problem hiding this comment.
I've suggested before that we might adopt a Java/Maven style approach to version numbering, where exactly one commit has a release version like "0.4.0", and the next commit has "0.5.0-SNAPSHOT".
The advantage of this is that a snapshot can never be mistaken for a release build.
Is there any mileage in doing this?
|
We have already tags to mark a commit so I don't think that we need so much to define a commit in this way. |
Mte90
approved these changes
Dec 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps current version from
0.3.5-alphato0.4.0-alpha. You can see all the changes in the linked issue