#360 openQA and branching SOP changes related to openQA at branch time
Opened by adamwill. Modified
adamwill/infra-docs-fpo openqa-update  into  master

Download 360.patch

This is a big update that's mainly about documenting all the tasks
related to openQA at branch time. We also add a couple of bits to
the releng SOP: one noting that co-ordination with quality and CI
folks is needed during branching, and one to get the fedfind
release metadata updated, which is a critical step that should
happen during branching. Currently I Just Know that this has to
happen, but we should write it down. This metadata file is not
templated in Ansible because that would cause it to be updated too
soon at release time (we need fedfind's stable release list to
change only when the new release is available in the mirror
system, for...reasons).

This also documents how we handle openQA needles, since I noticed
while writing the branching steps that it's not written down, and
drops the section about autocloudreporter as that's obsolete and
no longer used.

Signed-off-by: Adam Williamson awilliam@redhat.com

@jnsamyak Could you check this out?

FWIW, it looks fine to me. We can always refine it more after pushing it.

This now has conflicts when trying to merge it.

@adamwill can you rebase this?

Oh, I did all this twice? Hah.

https://pagure.io/infra-docs-fpo/pull-request/385 and https://pagure.io/infra-docs-fpo/pull-request/386 had probably most of what this has. We can look through and see if there's anything in this which isn't in those, but I'm gonna be honest, it is not super high priority right now.

Metadata