| ... | ... | @@ -165,9 +165,10 @@ The `main` branch contains the last stable version of openPASS. Thus, the `main` |
|
|
|
1. After the merge, the new release is tagged (in git) with the according version number. The release date is set by tacking the version number.
|
|
|
|
1. The release has to be built by manually starting the according CI job for the newly assigned tag. After successful completion, artifacts are available on the CI and on https://download.eclipse.org/openpass/release/opSimulation.
|
|
|
|
1. After tagging and building, a new release has to be created in GitLab. Release notes can be added here. The release is then associated to the git tag, see https://gitlab.eclipse.org/eclipse/openpass/opSimulation/-/releases.
|
|
|
|
1. Create a release on the Eclipse openPASS project page (https://projects.eclipse.org/projects/automotive.openpass)
|
|
|
|
1. Webpage updates:
|
|
|
|
- Update the download link
|
|
|
|
- Update the timeline with the new version
|
|
|
|
- Update the download link (https://openpass.eclipse.org/)
|
|
|
|
- Update the timeline with the new version (https://openpass.eclipse.org/working-group/#timeline)
|
|
|
|
1. Afterwards, the documentation has to be updated.
|
|
|
|
|
|
|
|
## Update of Documentation
|
| ... | ... | |
