Skip to content

Versioning #71

@K-Meech

Description

@K-Meech

How should we define releases for this repo?

From this pr: #70
We should define what exactly a release here means, as it makes most sense to use it to keep track of changes in the sepc (as defined by the jsonschema)
My initial thought was to create a 0.2.0 once the current spec is fixed (which I think is the case now).

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