Release-checklist.md

@@ -49,11 +49,33 @@
 
     5. Wait until the new version of the KYPO CRP instance is deployed. 
 
-4. Go through the related [milestone](https://gitlab.ics.muni.cz/groups/muni-kypo-crp/-/milestones) and check if the issues are resolved in the deployed KYPO instance. If so, close the issue. If not, report the issue to the responsible group leader and go back to the previous step.
+4. Inform others about deployed KYPO instance on staging server. Send a message to the channel KYPOLAB in MS Teams:
 
-5. Check if the documentation is up to date.
+```
+KYPOLAB na stránke https://stage.crp.kypo.muni.cz sa nachádza náhľad na release 21.06. Prosím vás skontrolujte, že všetky zmeny, ktoré ste požadovali/nahlásili sú implementované, nasadné a fungujú podľa vašich predstáv. 
+Inštancia obsahuje nasledujúcich používateľov: 
 
-6. Once everything is ready to be released, create release tags in format `YY.MM` from tags previously specified in the file [kypo-crp-deployment/provisioning/group_vars/all.yml](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-deployment/-/blob/master/provisioning/group_vars/all.yml) and again update the file with release tags.
+- name: user1
+  password: gD10ZENn0T
+- name: user2
+  password: vgcBNtpD6S
+...
+
+
+Nastavil som nasledujúce práva: 
+  * All Mighty Users - user1, user2, user3
+  * Instructor - user4, user5, user6
+  * Trainee - user7, user8, user9, user10
+
+Pokiaľ sa prihlásite pomocou MUNI OIDC a chcete si nastaviť iné práva ako trainee, využite jedného z All Mighty users.  
+
+```
+
+5. Go through the related [milestone](https://gitlab.ics.muni.cz/groups/muni-kypo-crp/-/milestones) and check if the issues are resolved in the deployed KYPO instance. If so, write comment `Verified on staging instance of KYPO CRP release YY.MM. The feature/bug/issue has been implemented/fixed/resolved in project {link to the project} tag X.Y.Z.` and close the issue. If not, report the issue to the responsible group leader and go back to the previous step.
+
+6. Check if the documentation is up to date.
+
+7. Once everything is ready to be released, create release tags in format `YY.MM` from tags previously specified in the file [kypo-crp-deployment/provisioning/group_vars/all.yml](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-deployment/-/blob/master/provisioning/group_vars/all.yml) and again update the file with release tags.
 
     * Java:
         * [user-and-group](https://gitlab.ics.muni.cz/muni-kypo-crp/backend-java/kypo2-user-and-group/-/tags/new)
@@ -79,7 +101,7 @@
     * Change one.
     ```
 
-7. Finally, merge the release issue and create a release tag on the [deployment project](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-deployment/-/tags/new) in the same format as the others `YY.MM`.
+8. Finally, merge the release issue and create a release tag on the [deployment project](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-deployment/-/tags/new) in the same format as the others `YY.MM`.
 
     For release notes, compose a changelog from all the previous changelogs and optionally changelog for the deployment project.