![]() |
CARTA Backend
The backend component of CARTA
|
In this document, 123 is a placeholder for the current release number, and 124 for the following release number.
dev
branch: update CHANGELOG.md
. Change the Unreleased
heading to 123.0.0-beta.1
.release/123.0
branch using the dev
branch.release/123.0
branch: update VERSION_ID
string in src/Util/App.h
to 123.0.0-beta.1
.v123.0.0-beta.1
tag using the release branch.dev
branch, and merge them into the release branch. Ideally, bump the version and create a new tag every time changes are merged. If you don't want to bump the version, remember to destroy and recreate the latest tag.dev
branch: update CHANGELOG.md
. Create a new Unreleased
section.This process should be followed if changes have to be made after the beta packages have already been published (or even provided to a limited number of users). If there are significant changes in dev
that should not be included in the beta release, follow the point release procedure instead (but adjust the version strings as required).
dev
.dev
branch: update CHANGELOG.md
. Change the Unreleased
heading to 123.0.0-beta.2
.dev
branch into the release/123.0
branch.release/123.0
branch: update VERSION_ID
string in src/Util/App.h
to 123.0.0-beta.2
.v123.0.0-beta.2
tag using the release branch.dev
branch, and merge them into the release branch. Ideally, bump the version and create a new tag every time changes are merged. If you don't want to bump the version, remember to destroy and recreate the latest tag.dev
branch: update CHANGELOG.md
. Change the Unreleased
heading to 123.0.0
.dev
branch into the release/123.0
branch.release/123.0
branch: update VERSION_ID
string in src/Util/App.h
to 123.0.0-rc.1
.v123.0.0-rc.1
tag using the release branch.dev
branch, and merge them into the release branch. Ideally, bump the version and create a new tag every time changes are merged. If you don't want to bump the version, remember to destroy and recreate the latest tag.release/123.0
branch: update VERSION_ID
string in src/Util/App.h
to 123.0.0
.v123.0.0
tag using the release branch.dev
branch: update VERSION_ID
string in src/Util/App.h
to 124.0.0-dev
.dev
branch: update CHANGELOG.md
. Create a new Unreleased
section.This process should be followed if important bug fixes have to be released after the final release packages have already been published (or even provided to a limited number of users). If there are no changes in dev
that should not be included in the point release, follow the additional beta release procedure instead (but adjust the version strings as required).
dev
. Cherry-pick them into the release branch.dev
branch: update CHANGELOG.md
. Move the cherry-picked changes from the Unreleased
section to a new 123.0.1
section under Unreleased
.release/123.0
branch: update CHANGELOG.md
. Copy only the 123.0.1
section from the changelog in the dev
branch.release/123.0
branch: update VERSION_ID
string in src/Util/App.h
to 123.0.1
.v123.0.1
tag using the release branch.dev
and the release branch, fix it in dev
and cherry-pick the changes into the release branch. If an issue is caused by changes in dev
which are not included in the point release, make the minimal required changes in the release branch. Ideally, bump the version and create a new tag every time changes are made. If you don't want to bump the version, remember to destroy and recreate the latest tag.