Update docs for latest beta guidelines
What does this MR do?
It updates the description template and devdocs to include the latest beta testing guidelines. (Forum instead of Slack) Plus I improved the docs files altogether while being at it.
How confident are you it won't break things if deployed?
99,9987%
How to test
- Checkout branch
update-beta-guidelines
locally - Review new devdocs pages
- Take code of new MR template, past it into any MR or issue description and preview changes
Checklist
-
added a test, or explain why one is not needed/possible... -
no unrelated changes -
asked someone for a code review -
set a "for:" label to indicate who will be affected by this change -
used "state:" labels to track this MR's state until it was beta tested -
added an entry to CHANGELOG.md
-
added a short text that can be used in the release notes -
Once your MR has been merged, you are responsible to create a testing issue in Beta Testing Repo: - Consider writing a detailed description in German.
- Describe in a few sentences, what should be tested from a user perspective.
- Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
- Be aware, that also non technical people should understand.
Release notes text in German
GitLab Beschreibungs Schablonen und die entsprechenden Dokumentationsseiten den neuen Beta Testing Richtlinien angepasst.
Edited by Thomas Hauschild