From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?ISO-8859-15?Q?Andreas_F=E4rber?= <afaerber@suse.de>
Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 13
Date: Tue, 13 Mar 2012 15:05:18 +0100
Message-ID: <4F5F541E.6040102@suse.de>
References: <87r4wyuh4w.fsf@elfo.elfo> <4F5E9352.1010806@suse.de> <4F5EAB42.7010208@codemonkey.ws>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: QUOTED-PRINTABLE
Cc: "Liu, Jinsong" <jinsong.liu@intel.com>,
	KVM devel mailing list <kvm@vger.kernel.org>,
	quintela@redhat.com, Jan Kiszka <jan.kiszka@siemens.com>,
	qemu-devel@nongnu.org, Igor Mammedov <imammedo@redhat.com>,
	Alexander Graf <agraf@suse.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Return-path: <kvm-owner@vger.kernel.org>
Received: from cantor2.suse.de ([195.135.220.15]:42633 "EHLO mx2.suse.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754451Ab2CMOFT (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 13 Mar 2012 10:05:19 -0400
In-Reply-To: <4F5EAB42.7010208@codemonkey.ws>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Am 13.03.2012 03:04, schrieb Anthony Liguori:
> On 03/12/2012 07:22 PM, Andreas F=E4rber wrote:
>> Am 12.03.2012 13:40, schrieb Juan Quintela:
>>> Please send in any agenda items you are interested in covering.
>>
>> * QEMU 1.1 roadmap
>>
>> If we're still aiming for a release in early May that would mean a
>> feature freeze in about four weeks.
>=20
> Soft freeze.  Hard freeze is about six weeks away.

Correct, and soft freeze defines itself as "Major features should have
initial code committed by this date."

I did consider all mentioned ones "major" features as opposed to random
bug fixes.

My goal would be to assemble a task list with dates and responsibilitie=
s
such as in my case, "have qom-cpu series merged <next Friday> by
<Anthony>", "Merge qom-cpu-arm through Peter's target-arm tree by <date=
>
pulled by <Blue>", ... that we can track and tick off. Who
reviews+merges x86, who mips+sh4/m68k/unicore32, do I merge ppc through
ppc-next (respectively s390x) in Alex' absence next week? When does x86
need to be merged to have enough time for hotplug?
Do we just aim for qtest inclusion or also for some more qtest-based
test coverage (needs time)? If we manage qemu-test, what additional
targets are missing and who covers them? etc.

Andreas

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