Use devel suffix for development #1278
Open
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
|
The downside of this proposal is when we change the MAJOR in MAJOR.MINOR.PATCH. We never did that yet and when we do the "devel" reference won't match the real release. I think that is acceptable because a development version won't be released. (I remember when Postgres used to use MAJOR.MINOR.PATCH and 8.5 was the reference for the next release until the community decided to call it 9.0.) |
The current version during development is the latest release version. That's not ideal because it confuses the stable release with a development code. The new policy states that for a release, we remove the "devel" suffix and the first commit after release is to (a) increment the major and/or minor version and (b) add the "devel" suffix back. It means if we release 1.24.0, the next commit after release should update version from 1.24.0 to 1.25devel.
eulerto
force-pushed
the
devel-version
branch
from
b9fbb19 to
cf988c1
Compare
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.
The current version during development is the latest release version. That's not ideal because it confuses the stable release with a development code.
The new policy states that for a release, we remove the "devel" suffix and the first commit after release is to (a) increment the major and/or minor version and (b) add the "devel" suffix back. It means if we release 1.24.0, the next commit after release should update version from 1.24.0 to 1.25devel.