From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:59218)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1T6Q4z-0005fb-7F
	for qemu-devel@nongnu.org; Tue, 28 Aug 2012 13:59:58 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1T6Q4u-0002iu-Te
	for qemu-devel@nongnu.org; Tue, 28 Aug 2012 13:59:57 -0400
Received: from cantor2.suse.de ([195.135.220.15]:34947 helo=mx2.suse.de)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1T6Q4u-0002in-Mt
	for qemu-devel@nongnu.org; Tue, 28 Aug 2012 13:59:52 -0400
Message-ID: <503D0713.3090302@suse.de>
Date: Tue, 28 Aug 2012 19:59:47 +0200
From: =?ISO-8859-1?Q?Andreas_F=E4rber?= <afaerber@suse.de>
MIME-Version: 1.0
References: <87ipc4gd35.fsf@elfo.mitica>
	<20120828133028.GB6223@otherpad.lan.raisama.net>
	<CAFEAcA8DVECZqi7mu5VzP7uds5YmUMVEOgO+4BMv6dPV=0XtQQ@mail.gmail.com>
	<20120828142707.GD6223@otherpad.lan.raisama.net>
In-Reply-To: <20120828142707.GD6223@otherpad.lan.raisama.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] KVM call agenda for Tuesda, August 28th
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, Juan Quintela <quintela@redhat.com>, qemu-devel@nongnu.org, KVM devel mailing list <kvm@vger.kernel.org>, Igor Mammedov <imammedo@redhat.com>

Am 28.08.2012 16:27, schrieb Eduardo Habkost:
> On Tue, Aug 28, 2012 at 02:55:56PM +0100, Peter Maydell wrote:
>> On 28 August 2012 14:30, Eduardo Habkost <ehabkost@redhat.com> wrote:
>>> - 1.2 branching, or creation of a "cpu-next" tree where "good to be
>>>   merged" patches can live until 1.2 is done;
>>
>> With 1.3 due for release in just over a week, it seems unlikely
>> that it's worth branching at this point...
>=20
> Well, the closer to the release, the smaller the cost of branching as w=
e
> won't have many patches entering the 1.2 branch, anyway.

The idea behind the new release model is to never branch for releases,
so that we can easily bisect between v1.2 and v1.3, both tags being on
the same branch. So I don't think a 1.2 branch is likely.

Andreas

--=20
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe=
rg