qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony Liguori <aliguori@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Planning for 0.13
Date: Tue, 5 Jan 2010 23:33:50 +0200	[thread overview]
Message-ID: <20100105213350.GC30921@redhat.com> (raw)
In-Reply-To: <4B4333DF.8090303@linux.vnet.ibm.com>

On Tue, Jan 05, 2010 at 06:43:11AM -0600, Anthony Liguori wrote:
> Hi,
>
> I hope everyone had a happy new year!  Now that we've finished the 0.12  
> release and most of us have had a nice break, I think it's time to start  
> planning for the next release.
>
> 0.12 felt a bit rushed to me.  I'd like to take a bit more time with  
> 0.13 and try to complete features a bit more than we did in 0.12.  So I  
> propose that we target 0.13 as a 6-month cycle and target a June 1st  
> release.  Based on the -rc process for 0.12, I would like to have a two  
> week -rc cycle for 0.13 but this time, absolutely no non-bug fixes past  
> freeze.  We got sloppy in 0.12 with this and we had some ugly  
> regressions in the final release.
>
> Here are the features that I'm aware of for 0.13.  Please add anything  
> you're working on and I'll try to centralize this somewhere.
>
>  - gPXE support for virtio-blk
>  - Helper based network setup
>  - Balloon driver statistics
>  - Fully supported QMP
>  - Live migration protocol support for subvendor versions (aka features)

pci compliance (virtio passing whql)
vepa networking
kvm irqchip

> Regards,
>
> Anthony Liguori
>

  parent reply	other threads:[~2010-01-05 21:36 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 12:43 [Qemu-devel] Planning for 0.13 Anthony Liguori
2010-01-05 12:44 ` [Qemu-devel] " Anthony Liguori
2010-01-05 20:50 ` [Qemu-devel] " Stefan Weil
2010-01-05 21:33 ` Michael S. Tsirkin [this message]
2010-01-06  0:32   ` [Qemu-devel] " Anthony Liguori
2010-01-06 10:49     ` Michael S. Tsirkin
2010-01-06 12:36       ` Anthony Liguori
2010-01-06 13:20         ` Michael S. Tsirkin
2010-01-06 13:34           ` Anthony Liguori
2010-01-06 13:55             ` Michael S. Tsirkin
2010-01-06 15:10               ` Anthony Liguori
2010-01-06 15:16                 ` Michael S. Tsirkin
2010-01-06 15:24                   ` Anthony Liguori
2010-01-06 15:41                     ` Michael S. Tsirkin
2010-01-06 17:19                       ` Jamie Lokier
2010-01-06 18:19                         ` Michael S. Tsirkin
2010-01-06 22:49                           ` Jamie Lokier
2010-01-06 23:59                             ` Michael S. Tsirkin
2010-01-06 19:48                 ` Paolo Bonzini
2010-01-06 19:54                   ` Michael S. Tsirkin
2010-01-06 19:59                     ` Paolo Bonzini
2010-01-06 20:07                       ` Michael S. Tsirkin
2010-01-06 23:00                     ` Jamie Lokier
2010-01-07  0:05                       ` Michael S. Tsirkin
2010-01-05 22:31 ` [Qemu-devel] " Aurelien Jarno
2010-01-06  2:46 ` Roy Tam
2010-01-06  9:37 ` Gerd Hoffmann
2010-01-06 15:34 ` Adam Litke
2010-01-12 13:43 ` Pasi Kärkkäinen
2010-01-12 15:07   ` Stefano Stabellini
2010-02-09 14:50   ` Artyom Tarasenko

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=20100105213350.GC30921@redhat.com \
    --to=mst@redhat.com \
    --cc=aliguori@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    /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).