Skip to content

Changes

Page history
Update Release checklist authored by Tomáš Sapák's avatar Tomáš Sapák
Hide whitespace changes
Inline Side-by-side
Release-checklist.md
View page @ be483069
......@@ -62,7 +62,9 @@
6. Wait until the new version of the KYPO CRP instance is deployed.
5. Inform others about the deployed KYPO instance on the staging server. Send a message to the channel KYPOLAB in MS Teams:
5. Run staging apply pipeline here - https://gitlab.ics.muni.cz/muni-kypo/deployment/terraform/muni-kypo-tf-kypo-content/-/pipelines to deploy MU provider to Keycloak.
6. Inform others about the deployed KYPO instance on the staging server. Send a message to the channel KYPOLAB in MS Teams:
```markdown
**KYPOLAB** na stránce **https://stage.crp.kypo.muni.cz** je k dispozici release `YY.MM`. Prosím zkontrolujte, že všechny požadované změny jsou implementované, nasazené a fungují.
......@@ -82,7 +84,7 @@
Pokud se přihlásíte pomocí MUNI OIDC a chcete přiřadit jiná práva než jen trainee, využite jednoho z All Mighty users.
```
6. Go through the related [milestone](https://gitlab.ics.muni.cz/groups/muni-kypo-crp/-/milestones) and check that all the issues are resolved in the deployed KYPO instance. If so, write the following comment.
7. Go through the related [milestone](https://gitlab.ics.muni.cz/groups/muni-kypo-crp/-/milestones) and check that all the issues are resolved in the deployed KYPO instance. If so, write the following comment.
```markdown
Verified on staging instance of KYPO CRP release YY.MM.
......@@ -92,9 +94,9 @@
Then close the issue. If not, report the issue to the responsible group leader and return to the previous step.
7. Check if the documentation is up to date.
8. Check if the documentation is up to date.
8. Once everything is ready to be released, create release tags in the format `YY.MM` from tags previously specified in the file [muni-kypo-tf-kypo-crp-kubernetes/-/blob/master/value-files/stage.yaml](https://gitlab.ics.muni.cz/muni-kypo/deployment/terraform/muni-kypo-tf-kypo-crp-kubernetes/-/blob/master/value-files/stage.yaml) and again update the file with release tags.
9. Once everything is ready to be released, create release tags in the format `YY.MM` from tags previously specified in the file [muni-kypo-tf-kypo-crp-kubernetes/-/blob/master/value-files/stage.yaml](https://gitlab.ics.muni.cz/muni-kypo/deployment/terraform/muni-kypo-tf-kypo-crp-kubernetes/-/blob/master/value-files/stage.yaml) and again update the file with release tags.
* Java:
* [user-and-group](https://gitlab.ics.muni.cz/muni-kypo-crp/backend-java/kypo-user-and-group/-/tags/new)
......@@ -130,7 +132,7 @@
* Issue one.
```
9. Finally, merge the release issue and create a release tag on the [helm project](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-helm/-/tags) in the same format as the others, `YY.MM`.
10. Finally, merge the release issue and create a release tag on the [helm project](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-helm/-/tags) in the same format as the others, `YY.MM`.
Compose release notes from all previous components and optionally from the deployment project.
......@@ -150,7 +152,7 @@
* Issue one.
```
10. Inform others about a new release of KYPO CRP. Send a message to the channel KYPOLAB in MS Teams:
11. Inform others about a new release of KYPO CRP. Send a message to the channel KYPOLAB in MS Teams:
```markdown
**KYPOLAB** vše potřebné je otagované.
......@@ -160,4 +162,4 @@
Věnujte prosím pozornost sekci **Upgrading from the previous version**, ve které jsou obsažené důležité informace při přechodu na novou verzi.
11. Contact Vojta Hamerský, who will create a tweet that we have released a new version of the KYPO CRP. Provide him with release notes, mainly the list of new features and their usage.
\ No newline at end of file
12. Contact Vojta Hamerský, who will create a tweet that we have released a new version of the KYPO CRP. Provide him with release notes, mainly the list of new features and their usage.
\ No newline at end of file