Quality Gate Testing PTDATA 1408 (#499)

* Update PR_Template_VersionUpgrade.md

* Update .github/PULL_REQUEST_TEMPLATE/PR_Template_VersionUpgrade.md

* Update .github/PULL_REQUEST_TEMPLATE/PR_Template_VersionUpgrade.md

* Update .github/PULL_REQUEST_TEMPLATE/PR_Template_VersionUpgrade.md

* Update .github/PULL_REQUEST_TEMPLATE/PR_Template_VersionUpgrade.md

.github/PULL_REQUEST_TEMPLATE/PR_Template_VersionUpgrade.md

@@ -15,9 +15,10 @@ All jobs with an `x` in the boxes were performed to the best of knowledge.
 <!--- Lets check everything before we continue. -->
 - This PR refers to a versioned Branch with a name and a version number in the form of N.n.n, e.g. "TC_3.2.1".
 - This PR has a clean meaningful commit history. Minor commits or commits without description have been squashed, at the latest now.
-- The GitHub Actions "TC version update" and "CI (FHIR Validation)" finished successfull, release version and date was updated accordingly.
+- The GitHub Actions "TC version update" and "CI (FHIR Validation)" finished successfully; release version and date was updated accordingly by release_publish.py (triggered by action)
 - Eventually, increase the dependency of to newer Basis Modul and Basispofil-de and possibly others (package json and sushi-config)
-- Run Python script in terminal and increment version --> Eventeu
+- [ ] All release note items have been annotated as `test modifiying` OR `test stable` (the annotation should already take place within tickets for tracking reasons) 
+- [ ] the release notes were reviewed with a person responsible for testing
 - [ ] New Release Notes were created, alined to the commit history. Possibly, if you want to check the release notes for completeness, check against automatic relesase note generation in GitHub. In Github, go to 
   - _-> Releases_ then _-> Draft a new release_ with the _Modul Name and Version_, then
   - _-> Target the main-Branch_ and _-> enter a new Tag according to the Version_, then click.