Skip to content

Correct branch name #678

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
PandaeDo merged 2 commits into from
May 11, 2026
+2 −3
Merged

Correct branch name #678

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
427cc18
correct branch name
RolandJentschETAS May 11, 2026
2a61889
correct branch name
RolandJentschETAS May 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions process/process_areas/release_management/release_concept.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,12 +112,11 @@ Branching Strategy

Branches:

* master: for implementation and documentation in development phase.
* main: for implementation and documentation in development phase.
* release/\*: Branches for distinct releases, named release/<version-number>, no functional changes, only bugfixes, quality and documentation improvements.


Workflow:

#. When ready for a new release, create a branch release/<version-number> from master (if needed).
#. When ready for a new release, create a branch release/<version-number> from main (if needed).
#. Perform final testing and adjustments on the release branch (test results should be available continuously, but maybe not all).
#. Tag the release in the release branch.
Loading