| ... | ... | @@ -185,7 +185,8 @@ The `main` branch contains the last stable version of openPASS. Thus, the `main` |
|
|
|
2. 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).
|
|
|
|
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 tagging a new release has the be created. The release is then associated to the tag, see https://gitlab.eclipse.org/eclipse/openpass/opSimulation/-/releases.
|
|
|
|
4. After tagging a new release has to be created. The release is then associated to the tag, see https://gitlab.eclipse.org/eclipse/openpass/opSimulation/-/releases.
|
|
|
|
4. Update the link to the pre-built version on the webpage.
|
|
|
|
5. Afterwards, the documentation has to be updated.
|
|
|
|
|
|
|
|
## Update of Documentation
|
| ... | ... | @@ -211,5 +212,4 @@ The Git server hosting the documentation can be found here: https://git.eclipse. |
|
|
|
- git add -A ("add everything")
|
|
|
|
- git commit -m "commit message"
|
|
|
|
- git push
|
|
|
|
- The documentation is automatically linked on the openPASS webpages
|
|
|
|
|
|
|
|
- The documentation is automatically linked on the openPASS webpages |
|
|
\ No newline at end of file |
