Improve Readiness review documentation
With the recent gitlab-sshd enablement rollback, the readiness review has been noted as a point of contention. Let's further refine our readiness review procedure.
- Call out items that should be noted as mandatory and will require some form of answer too before a service can continue into production
- Provide some tips so we avoid certain language that ensures that instead of writing , example TBD, or Idem, instead we will have a clear understanding of the current state
- Enforce that new issues shall be created for any sections that are not well defined or do not have clear enough answers
Also take the time to roll through the template that we provide and mark items as mandatory