From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Roth Subject: Re: [Qemu-devel] KVM call agenda for 2014-04-01 Date: Mon, 31 Mar 2014 14:57:59 -0500 Message-ID: <20140331195759.22831.40560@loki> References: <87mwg6ejn8.fsf@elfo.mitica> <533948B3.2070009@suse.de> <53396BF1.1050605@de.ibm.com> <53397B82.4050907@redhat.com> <53397FD5.5050802@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: "Anthony Liguori" , "Christian Borntraeger" , "Juan Quintela" , "KVM devel mailing list" , "qemu list" , "Stefan Hajnoczi" , "Anthony Liguori" , "Bruce Rogers" To: =?utf-8?q?Andreas_F=C3=A4rber?= , "Peter Maydell" , "Paolo Bonzini" Return-path: Received: from e34.co.us.ibm.com ([32.97.110.152]:48350 "EHLO e34.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751004AbaCaT6I convert rfc822-to-8bit (ORCPT ); Mon, 31 Mar 2014 15:58:08 -0400 Received: from /spool/local by e34.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 31 Mar 2014 13:58:07 -0600 Received: from b03cxnp07028.gho.boulder.ibm.com (b03cxnp07028.gho.boulder.ibm.com [9.17.130.15]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id A60D61FF0043 for ; Mon, 31 Mar 2014 13:58:04 -0600 (MDT) Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by b03cxnp07028.gho.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s2VJvHY02687344 for ; Mon, 31 Mar 2014 21:57:17 +0200 Received: from d03av02.boulder.ibm.com (localhost [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s2VJw26C012186 for ; Mon, 31 Mar 2014 13:58:04 -0600 In-Reply-To: <53397FD5.5050802@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: Quoting Andreas F=C3=A4rber (2014-03-31 09:46:45) > Am 31.03.2014 16:32, schrieb Peter Maydell: > > On 31 March 2014 15:28, Paolo Bonzini wrote: > >> I think it would be a good idea to separate the committer and rele= ase > >> manager roles. Peter is providing the community with a wonderful = service, > >> just like you were; putting too much work on his shoulders risks g= etting us > >> in the same situation if anything were to affect his ability to pr= ovide it. > >=20 > > Yes, I strongly agree with this. I think we'll do much better > > if we can manage to share out responsibilities among a wider > > group of people. >=20 > May I propose Michael Roth, who is already experienced from the N-1 > stable releases? Sure, I would be willing. >=20 > If we can enable him to upload the tarballs created from his tags tha= t > would also streamline the stable workflow while at it. Agreed, though I feel a little weird about creating releases for tags t= hat aren't in the official repo. Would that be acceptable from a community stand-point? I'm honestly not sure. Otherwise I think Anthony/Peter would probably still need to process a = pull for stable-y.x branch in advance before we do the tarball/release. Woul= d still help simplify things a bit though by keeping tasks compartmentali= zed. Anthony, Peter: in the past, prior to release, I just sent an email wit= h a pointer to my github branch with the stable release tagged. Would a p= roper pull request (with a for-stable-x.y tag or somesuch) be preferable? If we opt to align the stable repo updates with the actual release, wha= t kind of lead time would we need prior to actual release? >=20 > Regards, > Andreas >=20 > --=20 > SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg, Germany > GF: Jeff Hawn, Jennifer Guild, Felix Imend=C3=B6rffer; HRB 16746 AG N= =C3=BCrnberg