To build RC1 bits on CBS, we need to follow the steps below for each project:

1. Update releases in common.rc file
   e.g: https://review.rdoproject.org/r/c/rdo-infra/releng/+/54525
2. Add the new pubkey in edit_source_gpg_sign script
   e.g: https://review.rdoproject.org/r/c/rdo-infra/releng/+/54527
3. Cut rpm-master branch of distgit repo to create the <release>-rdo branch. This can be done with branching script from releng tooling, as an example, or manually by modifying config repo.

   bash scripts/new_release_scripts/branch_projects.sh --libs-clients
   bash scripts/new_release_scripts/branch_projects.sh --core
   

4. Submit review with send_new_version.sh script.
   Another way to submit patches is with _rdo_release_review _ provided by releng project
   e.g:

   rdo_release_review -u rdo-trunk -c RDO -e dev@lists.rdoproject.org -r $MASTER_RELEASE -t ${MASTER_RELEASE}-uc -d 21

Cross-tagging operation policy

• We don't cross-tag manually anymore.
• In order to tag an existing package built in the past, then we should cherry-pick the patch used to build it.
  e.g: https://review.rdoproject.org/r/c/openstack/observabilityclient-distgit/+/52899
  https://review.rdoproject.org/r/c/puppet/puppet-kmod-distgit/+/52882
  The CI/CD job will then realize the NVR already exists and will tag into the new release -candidate tag.
  If the operator wants to benefit patches that have landed in rpm-master in the meantime, then the operator should bump the release and add in changelog "Rebuild in <release>-rdo"
  e.g: https://review.rdoproject.org/r/c/openstack/tempest-distgit/+/54339/2/openstack-tempest.spec