Improve QA page

[aarnq]

Describe the bug

The Admin / QA page feels severely lacking, and it is not the current checklist we use for QA. Should we work towards it being it or should we at least piece together enough steps (by including from the user docs) to roughly cover what we do? @cristiklein

[cristiklein]

Hi @aarnq. Thanks for bringing this up, it was on my mind too.

I see the following options:

1. Public docs QA page = quality criteria (i.e., bare minimum)
2. Public docs QA page = quality criteria + overview of QA process
3. Public docs QA page = quality criteria + overview of QA process + detailed QA process

PM-wise I'd prefer (3). It would be great if we could show our customer not only what are the high-level quality criteria, but also allow them to verify that we implement them properly.

However, I'm unsure how easy it is to implement (3), given that right now the QA checklist is in a non-public issue template.

Would it make sense to move the release issue template (which includes the QA checklist) to public repos? If so, then we could link to those from the public docs QA page and it would look really good.

Here we would have two sub-choices:

3.a. Move release issue template to the compliantkubernetes repo 3.b. Create releases issue template in the relevant repo: compliantkubernetes-kubespray and compliantkubernetes-apps.

I think 3.a or 3.b should be a QA decision. I'm leaning towards 3.b.

What do you think?