Skip to content
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

Releases after 2.0 are not tagged #78

Open
codemedic opened this issue Mar 24, 2018 · 0 comments
Open

Releases after 2.0 are not tagged #78

codemedic opened this issue Mar 24, 2018 · 0 comments

Comments

@codemedic
Copy link

codemedic commented Mar 24, 2018

I know it is probably a subtle / insignificant thing in comparison to everything else about this project, but it is a good thing to do, especially for the sake of communicating various aspects of the library (API, ABI etc) and the stability from the PoV of authors and maintainers.

Something like semver would be a good, widely understood, versioning scheme to consider. Combine that with git-flow and it will make things easier to manage. At least that is the summary of what I have tried with other projects.

It for sure, will benefit anyone integrating with the library, looking for a later, stable version, without having to scan through the commit history to find the git-hash to freeze at.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant