| ... | ... | @@ -163,7 +163,7 @@ 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. Add the release notes.
|
|
|
|
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. Tag the release according to the convention a.b.c
|
|
|
|
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. Webpage updates:
|
|
|
|
- Update the download link
|
|
|
|
- Update the timeline with the new version
|
| ... | ... | |
