From 50317ec6d2469ec33760430dd45d58a1ed307487 Mon Sep 17 00:00:00 2001 From: Sebastian Niehus <165138846+SebastianNiehusAA@users.noreply.github.com> Date: Thu, 4 Apr 2024 12:07:31 +0200 Subject: [PATCH] doc(release): Remove confluence changelog from RELEASE.md. Adapt description of changelog creation. (#697) Task: IL-413 Co-authored-by: Sebastian Niehus --- RELEASE.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 5da29daad..dc3318c38 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -1,16 +1,11 @@ # Release cycle TODOs -- Prepare the changelog in some MD file - - **Ideally** the merge request messages should be in a format that allows you to just copy them into the changelog. -- Present the changelog in the daily. - Update CHANGELOG.md - - Use the prepared changelog and adjust based on feedback from the daily and new changes to the main branch since then. + - We committed to updating the changelog with every relevant merge into main. Check the new entries of the changelog and perform adjustments where necessary. - Update the "version" field of the project in `pyproject.toml` - We use [semantic versioning](https://semver.org/) - Commit the changes and merge to main - Create a new release tag in GitHub (Tags -> Releases -> Draft a new release) and save it as draft - Copy the changelog into the release description. Also add a link to the commits since the last release at the bottom of the description. -- Update changelog at https://aleph-alpha.atlassian.net/wiki/spaces/EN/pages/632520766/Changelogs. - - Best just copy over the changes from CHANGELOG.md and adjust the formatting. - Make sure the changes have been merged into the main branch. - Publish the release.