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

Releasing and tagging #102

Open
palmskog opened this issue Oct 17, 2019 · 0 comments
Open

Releasing and tagging #102

palmskog opened this issue Oct 17, 2019 · 0 comments

Comments

@palmskog
Copy link
Collaborator

palmskog commented Oct 17, 2019

To make the library easier to use for others, one option is to do explicit tags/releases in the repo that are guaranteed to work with a certain combination of versions of operating system + compiler + HOL4. Continuous integration and other tooling (discussed in #99) can be used to support generating these tags/releases.

Although always relying on HEAD of project's repo (like Google does internally) avoids problems with maintaining backwards compatibility, it typically comes at the cost of user flexibility.

One option for release naming is to use semantic versioning.

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