This page covers all the areas and components that need to be updated to accomodate a new upstream Ceph (lettered) release.

THIS IS NOT YET ALL ENCOMPASSING

We'll use Quincy as an example

1. The following files need to be modified in ceph-build.git

   ceph-api-nightly/config/definitions/ceph-api-nightly.yml
   ceph-build/config/definitions/ceph-build.yml
   ceph-dashboard-cephadm-e2e-nightly/config/definitions/ceph-dashboard-cephadm-e2e-nightly.yml
   ceph-dev-build/build/build_osc
   ceph-dev-build/build/setup_osc
   ceph-dev-cron/config/definitions/ceph-dev-cron.yml
   ceph-dev-new-trigger/config/definitions/ceph-dev-new-trigger.yml
   ceph-dev-trigger/config/definitions/ceph-dev-trigger.yml
   ceph-pr-api/config/definitions/ceph-pr-api.yml
   ceph-volume-test/config/definitions/ceph-volume-test.yml
   scripts/sign-rpms
   scripts/sync-push
   scripts/build_utils.sh

2. Add the release to chacra (Example)
3. Run https://jenkins.ceph.com/job/ceph-release-rpm/
   1. If you accidentally run the ceph job before the ceph-release-rpm job, you can run chacractl repo recreate ceph/quincy/c675060073a05d40ef404d5921c81178a52af6e0/centos/8 (for example) to get the ceph-release-rpm added to the repo
4. Add release to https://docs.ceph.com/en/latest/start/os-recommendations/#platforms
5. The longrunningcluster should be upgraded to the release candidate at least a week prior to the planned release date.