Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Releasing and tagging #102

Copy link
Copy link

Description

@palmskog
Issue body actions

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.

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    Morty Proxy This is a proxified and sanitized view of the page, visit original site.