Establish a release process for the ZTK itself
Registered by
Christian Theune
The ZTK needs a process that defines: when releases are cut, where the releases are published, how documentation about the release and its changes is created and distributed, how we update versions of dependency packages and other rules we need to check before creating a release.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Christian Theune
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)
