-
Notifications
You must be signed in to change notification settings - Fork 630
Announce Semantic Versioning scheme #468
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
Conversation
* `MINOR`: increased every christmas, may be API incompatible | ||
* `TEENY`: security or bug fix which maintains API compatibility | ||
* May be increased more than 10 (such as `2.1.11`), and will be released every 2-3 months. | ||
* `PATCH`: commits since last minor release, will remain at p0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"will remain at p0" is not clear to me (but I did not follow any discussions on this).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the existing version scheme: {MAJOR}.{MINOR}.{TEENY}-p{PATCH}
we will keep PATCH
at 0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to contradict https://gist.github.com/sorah/7803201:
"PATCHLEVEL: number of commits since last MINOR release (will be reset at 0 when releasing MINOR)"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stomar It is my mistake, I will fix it and update the meeting log upstream (where these notes came from)
Separate comment on tags and releases from branch list
@stomar Thanks for the review! ❤️ |
Looks good. 👍 |
@hsbt Are you ok to merge this? |
[WIP] Announce Semantic Versioning scheme
Pending review by @hsbt