Skip to content

Documents on release procedure and run examples #28

@dragonJACson

Description

@dragonJACson

Create some documents on how and when to release a new version.

For example, we’ve made QP a trait instead of a struct in up coming pull requests. That would break our APIs. Should we release a new version with v0.2.0, or just v0.1.1, because we haven’t released v1.0.0 yet? (v1.0.0 means stable API, while anything could happen in versions before v1.0.0)

Consider providing a Justfile for releasing and some automating works at the same time.

Metadata

Metadata

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions