Skip to content

Use semver even in minor updates #3936

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

Closed
nervo opened this issue Oct 4, 2017 · 4 comments
Closed

Use semver even in minor updates #3936

nervo opened this issue Oct 4, 2017 · 4 comments
Labels

Comments

@nervo
Copy link

nervo commented Oct 4, 2017

In order to ease maintenance, and continuous integrations, you should use semver even in minor updates.
That means no more 0.28 or 0.29release, but 0.28.0 and 0.29.0 :)

@bep
Copy link
Member

bep commented Oct 4, 2017

Point taken.

@bep bep closed this as completed Oct 4, 2017
@bep
Copy link
Member

bep commented Oct 4, 2017

Which is a way of saying we're not doing it: I'm not sure what it solves or makes easier, but I have logic in my release process that I'm not too interested in putting more work into to adapt to this, and ... I like them as is.

@nervo
Copy link
Author

nervo commented Oct 4, 2017

Seems legit, thx for clarification :)

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants