Skip to content

Define compatibility and release policy #17

Description

@darthfork

Consumers need to know which Bazel versions, Zig versions, and breaking-change rules apply.

Tasks:

  • Define semantic versioning policy.
  • Define supported Bazel range.
  • Define supported Zig versions.
  • Document deprecation expectations.

Acceptance criteria:

  • Compatibility policy is written down in the repo.
  • Releases can be evaluated against a documented support contract.

Parent issue: #5

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions