| ... | @@ -186,7 +186,8 @@ The `main` branch contains the last stable version of openPASS. Thus, the `main` |
... | @@ -186,7 +186,8 @@ The `main` branch contains the last stable version of openPASS. Thus, the `main` |
|
|
3. 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.
|
|
3. 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.
|
|
|
4. After the merge, the new release is tagged with the according version number. The release date is set by tacking the version number.
|
|
4. After the merge, the new release is tagged with the according version number. The release date is set by tacking the version number.
|
|
|
5. Afterwards, the documentation has to be updated.
|
|
5. Afterwards, the documentation has to be updated.
|
|
|
## Update the Documentation
|
|
|
|
|
|
## Update of Documentation
|
|
|
|
|
|
|
|
Step 1 is usually done by a committer. Step 2 should be done by the project lead.
|
|
Step 1 is usually done by a committer. Step 2 should be done by the project lead.
|
|
|
|
|
|
| ... | | ... | |
