In addition: container images can be pulled from - quay.ceph.io/ceph-ci/ceph:pacific-16.2.7_RC1 deb and rpm packages can be installed from - https://shaman.ceph.com/builds/ceph/pacific-16.2.7_RC1/fdc003bc12f1b2443c4596eeacb32cf62e806970/ - how to install development packages: https://docs.ceph.com/en/pacific/install/get-packages/#ceph-development-packages On Mon, Nov 29, 2021 at 9:23 AM Yuri Weinstein <yweinste@xxxxxxxxxx> wrote: > > Details of this release are summarized here: > > https://tracker.ceph.com/issues/53324 > Release Notes - https://github.com/ceph/ceph/pull/44131 > > Seeking approvals for: > > rados - Neha > rgw - Casey > rbd - Ilya, Deepika > krbd Ilya, Deepika > fs - Venky, Patrick > upgrade/nautilus-x - Neha, Josh > upgrade/pacific-p2p - Neha, Josh > > ======================== > We are also publishing a release candidate this time for users to try > for testing only. > > The branch name is pacific-16.2.7_RC1 > (https://shaman.ceph.com/builds/ceph/pacific-16.2.7_RC1/fdc003bc12f1b2443c4596eeacb32cf62e806970/) > > ***Don’t use this RC on production clusters!*** > > The idea of doing Release Candidates (RC) for point releases before > doing final point releases was discussed in the first-ever Ceph User + > Dev Monthly Meeting. Everybody thought that it was a good idea, to > help identify bugs that do not get caught in integration testing. > > The goal is to give users time to test and give feedback on RC > releases while our upstream long-running cluster also runs the same RC > release during that time (period of one week). We will kick this > process off with 16.2.7 and the pacific-16.2.7_RC1 release is now > available for users to test. > > Please respond to this email to provide any feedback on issues found > in this release. > > Thx > YuriW _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
