From: "Andreas Färber" <afaerber@suse.de>
To: Anthony Liguori <anthony@codemonkey.ws>
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>
Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 13
Date: Tue, 13 Mar 2012 15:05:18 +0100 [thread overview]
Message-ID: <4F5F541E.6040102@suse.de> (raw)
In-Reply-To: <4F5EAB42.7010208@codemonkey.ws>
Am 13.03.2012 03:04, schrieb Anthony Liguori:
> On 03/12/2012 07:22 PM, Andreas Färber 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.
>
> 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 responsibilities
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
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-03-13 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 12:40 KVM call agenda for Tuesday 13 Juan Quintela
2012-03-13 0:22 ` Andreas Färber
2012-03-13 2:04 ` [Qemu-devel] " Anthony Liguori
2012-03-13 14:05 ` Andreas Färber [this message]
2012-03-13 13:31 ` Eduardo Habkost
2012-03-13 13:54 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2011-12-12 23:16 Juan Quintela
2011-12-12 23:31 ` [Qemu-devel] " Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F5F541E.6040102@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=imammedo@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=jinsong.liu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).