Skip to content

Commit 47896cc

Browse files
authored
docs: how to release (#4255)
* docs: release management * Update release-management.md * Update release-management.md * Update release-management.md * Update release-management.md * Update release-management.md * Update release-management.md * Update release-management.md
1 parent a1070d4 commit 47896cc

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

docs/release-management.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# Release Management
2+
3+
We aim to provide reliable and consistent releases. Due to dependencies on other projects, as well as our roadmap, we need to actively manage releases and decide on their scope. This is done through frequent alignments.
4+
5+
In order to support this process, and to gain some insight into the current state of issues, we need to both "tag" and track issues in a standardised and normative wording.
6+
7+
To do this, we
8+
- use semantic versioning wording in our pull request titles ([`fix: `](https://github.com/db-ux-design-system/core-web/blob/main/docs/conventions.md?plain=1#L11) for bugfixes that would be published in a patch release, and [`refactor: `](https://github.com/db-ux-design-system/core-web/blob/main/docs/conventions.md?plain=1#L11) or [`feat: `](https://github.com/db-ux-design-system/core-web/blob/main/docs/conventions.md?plain=1#L11) for targeting minor releases).
9+
- still leave them in draft state even when setting it to "in review" state in the [UX Engineering Team Backlog board](https://github.com/orgs/db-ux-design-system/projects/6/views/1)
10+
- set their status in the [UX Engineering Team Backlog board](https://github.com/orgs/db-ux-design-system/projects/6/views/1) to "ready for release" after reviewing them, so that we have a clear overview of the candidates for the next releases.
11+
12+
Both the release scope, ensuring that all issues are ready for release, and even also other issues candidates might get pushed to that state, and the merging of Pull Requests on release day are managed by a Release Manager.
13+
14+
## Repositories
15+
16+
You would still need to check all repositories for release candidates, that might not be listed within [UX Engineering Team Backlog board](https://github.com/orgs/db-ux-design-system/projects/6/views/1) to "ready for release" column: <https://github.com/db-ux-design-system/.github-private/blob/main/profile/README.md#repositories-mit-ggf-weiteren-release-relevanten-prs>

0 commit comments

Comments
 (0)