Absolutely. I always say to upgrade production when there’s a compelling reason. A new dot release — of any software — is not in isolation compelling. Bug fixes may be, as may new features. That said, we only learn of issues when new releases are stressed in diverse environments. Upstream performs exhaustive regression tests but can’t always model every permutation of use case and cluster history. So there’s a lot of value in smoke testing in dev and staging clusters.
> On May 25, 2025, at 4:41 AM, Konstantin Shalygin <k0...@k0ste.ru> wrote: > > Hi, > > Thanks for the perfect overview of the Reef release! I'll steal this as is > for the slide, for another overview of why it's important to have an update > strategy. Sometimes folks don't understand why our 75 clusters are using the > Nautilus or Pacific release > > > Thanks, > k > Sent from my iPhone > >> On 25 May 2025, at 10:18, Janne Johansson <icepic...@gmail.com> wrote: >> >> No, I did not experience ALL these issues myself - only some of them - >> but its been quite the time to get the popcorn.. > _______________________________________________ > ceph-users mailing list -- ceph-users@ceph.io > To unsubscribe send an email to ceph-users-le...@ceph.io _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
