Skip to content

Create Documentation for new Release process #853

@morri-son

Description

@morri-son

Description
Document the new release process with a focus on the WHAT, so every release responsible is able to savely execute it (even when only happening once in a quarter). The process for ocm v1 should act as basis. The document should be in markdown format.

The document needs to be linked in our "How we work" Slack document and needs to become part of the sprint responsibility, as in the future releases for old and new OCM have to be done.

Done Criteria

  • Document available in the repo
  • Use new document to explain new process in an onboard meeting

Metadata

Metadata

Assignees

Labels

area/ipceiImportant Project of Common European Interestkind/tasksmall task, normally part of feature or epic

Type

No fields configured for Task.

Projects

Status
🍺 Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions