Ceph » Stable releases

To be clear, the flow is such:

1. The build lead starts the build job, as defined in https://docs.ceph.com/en/latest/dev/release-process/#starting-the-build
   1. See https://jenkins.ceph.com/view/all/job/ceph/build?delay=0sec
2. This job builds the distros, then leads to the jenkins tag job.
3. The tag job (https://jenkins.ceph.com/job/ceph-tag/) creates the version tag commit and pushes it to https://github.com/ceph/ceph-releases/tags and https://github.com/ceph/ceph/tags.

The issue with this flow is that if we ever get to the point where we need to redo a part of the release (as with v18.2.1), we don't want the tag to be pushed right away to https://github.com/ceph/ceph/tags. The ideal result would be to preserve the action that pushes the tag to https://github.com/ceph/ceph-releases/tags, and then let a Ceph developer manually push the tag from ceph-releases to https://github.com/ceph/ceph/tags once we're sure the release is ready.

The fix would involve modifying one or more of the ansible role definitions, which I believe are defined here: https://github.com/ceph/ceph-build/tree/main/ansible/roles/ceph-release/tasks