Skip to content

Maru versioning #452

@Filter94

Description

@Filter94

Description

We need a way to properly version Maru

Motivation

We need it so:

  • it's easy to tell which Maru version is considered stable
  • when it's time to upgrade
  • Easy to tell whether there are any breaking changes looking at the version

Tasks

  • Automate the versioning
  • Test it
  • Describe the release process in a document in the repo

Acceptance criteria

  • Maru has releases, version and the release process

Risks

  • ???

Remember to

  • Add the documentation label in case there is an impact on the documentation
  • Add priority and team labels
  • Add Task for updating the Runbook or adding/updating existing metrics and alerts.

Metadata

Metadata

Assignees

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