Is there a plan for how it's going to be maintained and updated? Is that on file with rel-eng's approval? Are you asking for this to be treated as a blocking deliverable for Fedora 30? (It's far too late to be considered so for F29.)

The idea is to integrate pushing images to quay on the releng script that pushes images to registry.fp.o so it would be maintained and updated on the same way.

For f29, the container images are not release blocking deliverables and there is no any reference about the registries where they should be available or no: https://fedoraproject.org/wiki/Releases/29/ReleaseBlocking#Container

I am not asking for anything else than being able to publish to quay.io :smile:

As @jlanda mentioned it is using the same script/process that is currently used to publish the base image on registry.fp.o.

None of the container images are release blocking and I am happy to keep it that way.

Works for me. +1

We have all the setup ready, I just wanted to get the confirmation from FESCo since we will be publishing to a non FOSS service, which we already do for docker hub.

+1

+1

+1

+1 here as well.

I don't know of a reason you would need FESCo approval to do this since we already publish our content on other non-FOSS systems, but +1.

A week has passed. Approved: +6, 0, 0.

Needs to remain open until the announcement goes out.