All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Andreas Färber" <afaerber@suse.de>
Cc: quintela@redhat.com, "Liu, Jinsong" <jinsong.liu@intel.com>,
	KVM devel mailing list <kvm@vger.kernel.org>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	qemu-devel@nongnu.org, Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 13
Date: Mon, 12 Mar 2012 21:04:50 -0500	[thread overview]
Message-ID: <4F5EAB42.7010208@codemonkey.ws> (raw)
In-Reply-To: <4F5E9352.1010806@suse.de>

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.

>
> http://wiki.qemu.org/Planning/1.1

Yup.

>
> My stake is that I'd like to see CPUs and machines QOM'ified for 1.1,
> and I'm aware that also CPU hot-plug and CPU versioning features depend
> on it. Not sure what timeline the respective authors have in mind, but
> IMO we should start counting backwards when series need to be finalized
> on the list and by whom they should get merged. Easter is on April 8th
> this year!
>
> Other features that I have in mind are qtest, qemu-test, gtk-doc and 4th
> QOM series. Not sure which of those were meant for 1.1.

My personal development priorities are qtest, and qbus (4th QOM series). 
qemu-test and gtk-doc are both nice to haves but I have a sneaking suspicion 
that they're going to require a non-trivial amount of work.

>
> With the Wiki closed, having contributors add Feature pages for their
> 1.1 wishlist, as done for 1.0, is probably not going to work well, but
> collecting a rough list or dependency tree would be nice for planning.

The wiki isn't closed...  I would hope most contributors would have an account 
and/or would not have a problem asking for an account.

Regards,

Anthony Liguori

>
> Andreas
>


WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Andreas Färber" <afaerber@suse.de>
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>
Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 13
Date: Mon, 12 Mar 2012 21:04:50 -0500	[thread overview]
Message-ID: <4F5EAB42.7010208@codemonkey.ws> (raw)
In-Reply-To: <4F5E9352.1010806@suse.de>

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.

>
> http://wiki.qemu.org/Planning/1.1

Yup.

>
> My stake is that I'd like to see CPUs and machines QOM'ified for 1.1,
> and I'm aware that also CPU hot-plug and CPU versioning features depend
> on it. Not sure what timeline the respective authors have in mind, but
> IMO we should start counting backwards when series need to be finalized
> on the list and by whom they should get merged. Easter is on April 8th
> this year!
>
> Other features that I have in mind are qtest, qemu-test, gtk-doc and 4th
> QOM series. Not sure which of those were meant for 1.1.

My personal development priorities are qtest, and qbus (4th QOM series). 
qemu-test and gtk-doc are both nice to haves but I have a sneaking suspicion 
that they're going to require a non-trivial amount of work.

>
> With the Wiki closed, having contributors add Feature pages for their
> 1.1 wishlist, as done for 1.0, is probably not going to work well, but
> collecting a rough list or dependency tree would be nice for planning.

The wiki isn't closed...  I would hope most contributors would have an account 
and/or would not have a problem asking for an account.

Regards,

Anthony Liguori

>
> Andreas
>

  reply	other threads:[~2012-03-13  2:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 12:40 KVM call agenda for Tuesday 13 Juan Quintela
2012-03-12 12:40 ` [Qemu-devel] " Juan Quintela
2012-03-13  0:22 ` Andreas Färber
2012-03-13  0:22   ` [Qemu-devel] " Andreas Färber
2012-03-13  2:04   ` Anthony Liguori [this message]
2012-03-13  2:04     ` Anthony Liguori
2012-03-13 14:05     ` Andreas Färber
2012-03-13 14:05       ` Andreas Färber
2012-03-13 13:31   ` Eduardo Habkost
2012-03-13 13:31     ` Eduardo Habkost
2012-03-13 13:54   ` Michael S. Tsirkin
2012-03-13 13:54     ` [Qemu-devel] " Michael S. Tsirkin
  -- strict thread matches above, loose matches on Subject: below --
2011-12-12 23:16 Juan Quintela
2011-12-12 23:31 ` Anthony Liguori
2011-12-12 23:31   ` 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=4F5EAB42.7010208@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=afaerber@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.