This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
tasks:ceph-release-faq [2023/11/21 18:13] ljflores |
tasks:ceph-release-faq [2023/11/21 18:14] (current) ljflores |
||
---|---|---|---|
Line 23: | Line 23: | ||
- The only reason you’d want to do this step more than once for a release is to update /etc/yum.repos.d/ceph.repo. But occurrences of this are rare. | - The only reason you’d want to do this step more than once for a release is to update /etc/yum.repos.d/ceph.repo. But occurrences of this are rare. | ||
- What happens if a last minute PR needs to be added to a release after the build process has begun? | - What happens if a last minute PR needs to be added to a release after the build process has begun? | ||
- | - As long as all build artifacts are in the staging area and are not released to the public, we can follow this procedure: | + | - As long as all build artifacts are in the staging area and are not officially released, we can follow this procedure: |
- Delete the tag on https://github.com/ceph/ceph/tags and https://github.com/ceph/ceph-releases/tags | - Delete the tag on https://github.com/ceph/ceph/tags and https://github.com/ceph/ceph-releases/tags | ||
- Close the tag PR in https://github.com/ceph/ceph/pulls | - Close the tag PR in https://github.com/ceph/ceph/pulls | ||
- Redo the build step of the release process (https://docs.ceph.com/en/latest/dev/release-process/#starting-the-build) as normal, with `TAG` checked. | - Redo the build step of the release process (https://docs.ceph.com/en/latest/dev/release-process/#starting-the-build) as normal, with `TAG` checked. | ||
- If we need to add a new distro, we need to update it like in this PR: https://github.com/ceph/chacra/pull/307/files | - If we need to add a new distro, we need to update it like in this PR: https://github.com/ceph/chacra/pull/307/files |