Open Stack

On Thu, 27 Feb 2020 at 15:11, Thierry Carrez <thierry at openstack.org> wrote:
>
> Pierre Riteau wrote:
> > If you only want to create tags in these repositories, and don't need
> > tarball and PyPI releases, you could follow the approach used for
> > kayobe-config repositories with the no-artifact-build-job flag:
> > https://review.opendev.org/#/c/700174/2/deliverables/train/kayobe.yaml
> If I understand correctly, this flag only avoids failing tests if no
> release job is defined in Zuul for the repository (which is one of the
> things the release test jobs check for). It would not prevent defined
> release jobs from running if you added a tag.
>
> The way we've been handling this in the past was to ignore past releases
> (since they are not signed by the release team), and push a new one
> through the releases repository. It should replace the unofficial one in
> PyPI and make sure all is in order.
>
> In parallel, remove the "deprecated" flag from governance.

My bad, I misunderstood the problem. From now on I shall drink my
morning coffee before replying to the list.