Re: hammer 0.94.10 QE status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I've no idea what's broken there, so eg more valgrind failures are not
a big deal, but if the upgrade itself is failing in some way that's
going to be a problem. o_O

Hi Greg,

Let me try to clarify :-)

If someone reports problems upgrading their firefly cluster to hammer, and the problem is in firefly, will we publish a new firefly release?

If someone reports problems upgrading their dumpling cluster to firefly, and the problem is in dumpling, will we publish a new dumpling release?

I don't know the answer to those questions, but such a release -- if published -- would be "out-of-band" with regard to what is written in https://github.com/ceph/ceph/blob/master/doc/releases.rst#understanding-the-release-cycle - in particular this:

"Every other stable releases is a LTS (Long Term Stable) and will receive updates until two LTS are published. For instance Dumpling is retired when Hammer is published, Firefly is retired when Jewel is published etc."

Nathan
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux