From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nathan Cutler Subject: Re: hammer 0.94.10 QE status Date: Fri, 17 Feb 2017 20:52:58 +0100 Message-ID: <9c713c1b-b01b-ed10-dc06-6ffc5e9f0aa6@suse.cz> References: <90f9fb1d-74fa-3ae0-e5b7-186e5d1b2638@suse.cz> <22868a53-b99e-0686-e7e1-a288558aed27@suse.cz> <473edf7d-c46a-be4c-bc8a-35be4c095b2b@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de ([195.135.220.15]:51364 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932606AbdBQTxE (ORCPT ); Fri, 17 Feb 2017 14:53:04 -0500 In-Reply-To: Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Gregory Farnum Cc: Yuri Weinstein , Orit Wasserman , Sage Weil , Tamilarasi Muthamizhan , Ilya Dryomov , "Durgin, Josh" , "Just, Samuel" , "Dillaman, Jason" , John Spray , "Sadeh-Weinraub, Yehuda" , "ceph-devel@vger.kernel.org" > 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