adamwill reported a new issue against the project: `releng` that you are following:
``
So yesterday @mkolman pinged and told me a [new anaconda update for Fedora
26](https://bodhi.fedoraproject.org/updates/FEDORA-2017-10db06fadf) was available.
Here's what happens next:
* I manually create a Workstation live image containing that anaconda.
* I manually create a Server or Everything netinst image containing that anaconda.
* I scp these images over to the openQA staging server.
* I manually trigger an openQA test run on those images.
* I manually examine the results and post karma to Bodhi.
This is all very silly and shouldn't happen. What should happen (IMHO) is that, when
updates to certain packages appear, some releng bot should automatically produce a
slimmed-down compose (maybe just those two images, maybe also a couple others, not sure).
Then I could adapt the openQA update testing stuff to wait for the compose to appear and
automatically run appropriate tests on it. Then we could all go get a drink.
Can we do this? What bits are needed? A compose profile (like `Fedora`, `Fedora-Atomic`,
`Fedora-Cloud` etc.)? A fedmsg consumer to listen for update events and fire off a compose
using that profile? Any other bits I'm not aware of?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6746