Release-checklist.md

@@ -30,7 +30,21 @@
 
 3. Once the release branch is ready to be merged, deploy the KYPO instance on the staging server and check whether the KYPO CRP works properly.
 
-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.
+    1. Change the variable `kypo_crp_ansible_commit` in the file [muni-kypo-tf-kypo-crp/tfvars/stage.tfvars](https://gitlab.ics.muni.cz/muni-kypo/deployment/terraform/muni-kypo-tf-kypo-crp/-/blob/master/tfvars/stage.tfvars) to the release branch.
+
+    2. Check the Gitlab CI pipeline for the previous change and wait until all the stages up to the last are checked.
+
+        ![image](uploads/20d9e942def4425826c4902a17a8f182/image.png)
+
+    3. Jobs of the last stage are manual. Click on the gear icon and select **apply-stage** to run deployment Ansible provisioning.
+
+        ![Screenshot_from_2021-06-03_17-57-35](uploads/ae6fbf543fe7bfc2cf0ad86b237af467/Screenshot_from_2021-06-03_17-57-35.png)
+
+        **Note**: Optionally you can select **redeploy-stage**, which will first destroy all related cloud resources, including KYPO Head, and start from scratch. Do not use this option too frequently. We have a limit on certificate generation.
+
+    4. 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.
 
 5. Check if the documentation is up to date.