From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nathan Cutler Subject: Re: [ceph-users] v0.94.6 Hammer released Date: Mon, 29 Feb 2016 16:49:29 +0100 Message-ID: <56D46889.3000406@suse.cz> References: <1456736629334.47610@croc.ru> <191489558.55229005.1456744289131.JavaMail.zimbra@redhat.com> <1456745435596.21796@croc.ru> <56D45CCC.8010608@dachary.org> 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]:36911 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751979AbcB2Pth (ORCPT ); Mon, 29 Feb 2016 10:49:37 -0500 In-Reply-To: <56D45CCC.8010608@dachary.org> Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Loic Dachary Cc: Dan van der Ster , Odintsov Vladislav , Shinobu Kinjo , "ceph-devel@vger.kernel.org" , "Franklin M. Siler" , Sage Weil , Xiaoxi Chen , ceph-users > The basic idea is to copy the packages that are build by gitbuilders or by the buildpackage teuthology task in a central place. Because these packages are built, for development versions as well as stable versions[2]. And they are tested via teuthology. The packages that are published on http://ceph.com/ are rebuilt from scratch, using the process that Alfredo described. This is fine for the supported platforms and for the stable releases. But for the development releases and the platforms that are no longer supported but still built by gibuilders, we could just copy the packages over. > > Does that sound sensible ? Hi Loic: Community packages for "deprecated" platforms ("deprecated" in the sense that the Ceph developers are no longer testing on them) would be welcomed by many, I imagine. And the additional workload for the Stable Releases team is not large. The question is, where will the packages be copied *to*? -- Nathan Cutler Software Engineer Distributed Storage SUSE LINUX, s.r.o. Tel.: +420 284 084 037