Home.md

@@ -176,3 +176,12 @@ The DoD defines all requirements that need to be fulfilled for a contribution. A
 - Copyright Headers are updated
 - Contribution Questionnaires (CQ) for new third party dependencies are created and approved
 - Code has been formatted automatically using clang format
+
+## Guideline: Steps towards a new release
+
+The `main `branch contains the last stable version of openPASS. Thus, the `main `branch is representing the official releases of openPASS and is being tagged accordingly (e.g. v0.7, v0.8, …). New features for the next version are developed in the `develop `branch before they are pushed to the `main `branch. To release a new version within the Eclipse infrastructure, certain steps must be followed:
+
+1. Please read in the [Eclipse handbook](https://www.eclipse.org/projects/handbook/#release) the chapter about releases. The chapter contains detailed information about release reviews which should be performed for each major release. For a minor release it is sufficient to trigger a release review every year. After a successful release review for a minor release, an unlimited number of minor releases can be published for that year.
+1. Release reviews are created as an issue in GitLab. As a reference, the release review for v0.8 can be found [here](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/85).
+1. After all relevant commits for the new version has been pushed to the `develop `branch, the `develop `branch may be only merged to the `main `branch when the CI is green.
+1. After the merge, the new release is tagged with the according version number. The release date is set by tacking the version number.
\ No newline at end of file