[ceph-users] ceph 12.2.9 release
adeza at redhat.com
Thu Nov 8 04:40:58 PST 2018
On Thu, Nov 8, 2018 at 3:02 AM Janne Johansson <icepic.dz at gmail.com> wrote:
> Den ons 7 nov. 2018 kl 18:43 skrev David Turner <drakonstein at gmail.com>:
> > My big question is that we've had a few of these releases this year that are bugged and shouldn't be upgraded to... They don't have any release notes or announcement and the only time this comes out is when users finally ask about it weeks later. Why is this not proactively announced to avoid a problematic release and hopefully prevent people from installing it? It would be great if there was an actual release notes saying not to upgrade to this version or something.
> I think the big question is why do these packages end up publicly so
> that scripts, updates and anyone not actively trying to hold back get
> exposed to them, then we are somehow supposed to notice that the
> accompanying release notes are lacking and then from that divinate
> that we shouldn't have upgraded into this release at all. This seems
> all backwards in most possible ways.
> I'm not even upset about releases having bugs, stuff happens, but the
> way people are forced into it, then it's somehow your fault for
> running ceph-deploy or yum/apt upgrade against official release-repos.
It isn't your fault (or anyone in the community), we don't have a good
system in place for community repos to manage it in a way that would
help when problems like this come up.
We are in a much better place than a few years ago though, when
packages had to be placed manually when creating repos, but more work
is needed to address multi-version support in deb repos
and yanking known bad versions out of the official/latest release location.
> It's almost as if it was meant to push people into slow-moving dists
> like Blue^H^H^H^HRedhat with ceph on top.
> May the most significant bit of your life be positive.
> ceph-users mailing list
> ceph-users at lists.ceph.com
More information about the ceph-users