We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi @alatas,
The reason I'm asking #1 is that I want to base my work on your project, so I need to know if it OK doing so.
Now, to base my work on your project, could you adapt a semantic versioning scheme to your release please?
Best Practices When Versioning a Release https://blog.codeship.com/best-practices-when-versioning-a-release/
I.e., would you give your releases version number of MAJOR.MINOR(.PATCH) please? If OK, would you publish a new release of '3.0.0' or '3.0' please?
MAJOR.MINOR(.PATCH)
3.0.0
3.0
Thanks a lot
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi @alatas,
The reason I'm asking #1 is that I want to base my work on your project, so I need to know if it OK doing so.
Now, to base my work on your project, could you adapt a semantic versioning scheme to your release please?
Best Practices When Versioning a Release
https://blog.codeship.com/best-practices-when-versioning-a-release/
I.e., would you give your releases version number of
MAJOR.MINOR(.PATCH)
please?If OK, would you publish a new release of '
3.0.0
' or '3.0
' please?Thanks a lot
The text was updated successfully, but these errors were encountered: