qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Mark McLoughlin <markmc@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Cutting a new QEMU release
Date: Mon, 09 Feb 2009 15:36:37 -0600	[thread overview]
Message-ID: <4990A1E5.8050809@codemonkey.ws> (raw)
In-Reply-To: <1234183414.13728.30.camel@blaa>

Mark McLoughlin wrote:
> On Tue, 2009-02-03 at 14:48 -0600, Anthony Liguori wrote:
>   
>> What do people think?  TCG seems to be in a good place.  We've got 
>> virtio, KVM, live migration, tons of new devices, bsd-user, etc.
>>
>> We could decide to cut one by the end of the month.  I'm already doing 
>> some test work in QEMU so I can follow up with some more detailed notes 
>> about what is working and what isn't working.  That gives us some time 
>> to decide if there's anything we need to fix before a release.
>>     
>
> Sounds great to me.
>
> >From a Fedora perspective, qemu-0.9.1 is a year old and upstream has
> moved on a lot. As a package maintainer, it's hard to justify caring too
> much about bugs reported against 0.9.1, since the bug is likely to have
> very little relevance to the latest upstream.
>
> Also, it would be really nice to have a kvm-userspace based off a solid
> qemu release ... qemu moving so fast is great, but it means it's hard to
> predict the stability of a given kvm-userspace release.
>
> Some questions:
>
>   - Will there be a period before the release when only bug fixes are 
>     merged?
>   

It's a good idea, but it may be hard to pull off practically speaking 
for the first release.  Let's see how it works out.

>   - Will there be a release candidate?
>   

Sometime this week, I'll try to post something summarizing our current 
state and anything outstanding.  If there's time to put out an -rc, I'll 
try to make one available.  Things may hiccup a bit.

>   - Is there any missing features that we might push out the release
>     date for?
>   

Personally, I don't think so.  I think openbios was the biggest issue 
because we don't have the code for the current firmware.  It looks like 
that's been almost resolved.  I'm more interested in getting a release 
out in a timely manner than holding up for any particular feature.

If we have lots of features going in, I'd rather do more frequent 
releases than hold up releases.

>   - Post-release, is there any interest in maintaining a stable branch 
>     until the next release?
>   

I am tempted to try it out.  Let's see how it goes.

>   - The plan for the next release is roughly 6 months, yes?
>   

Yup.

Regards,

Anthony Liguori

> Thanks,
> Mark.
>
>
>
>   

  reply	other threads:[~2009-02-09 21:37 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-03 20:48 [Qemu-devel] Cutting a new QEMU release Anthony Liguori
2009-02-03 20:58 ` Glauber Costa
2009-02-03 21:35   ` Laurent Desnogues
2009-02-03 21:50     ` Anthony Liguori
2009-02-03 22:05       ` Laurent Desnogues
2009-02-03 22:47         ` Anthony Liguori
2009-02-03 23:48           ` Glauber Costa
2009-02-04 13:09       ` Ulrich Hecht
2009-02-04  0:31     ` David Turner
     [not found]     ` <74222928-D24B-4780-BDB0-D537A83C4F68@hotmail.com>
2009-02-04  5:08       ` C.W. Betts
2009-02-03 21:48 ` Rick Vernam
2009-02-03 22:07 ` Daniel P. Berrange
2009-02-04 14:50 ` Aurelien Jarno
2009-02-04 15:23   ` Tristan Gingold
2009-02-04 15:43     ` Lennart Sorensen
2009-02-04 16:01       ` Tristan Gingold
2009-02-04 18:17         ` [Qemu-devel] " Consul
2009-02-04 17:39   ` [Qemu-devel] " Blue Swirl
2009-02-04 17:50     ` Jonathan Kalbfeld
2009-02-04 20:07   ` Blue Swirl
2009-02-07 14:15   ` Stuart Brady
2009-02-04 15:58 ` Glauber Costa
2009-02-07 15:29 ` Shin-ichiro KAWASAKI
2009-02-11 21:49   ` Rob Landley
2009-02-12 14:44     ` Shin-ichiro KAWASAKI
2009-02-12 21:08       ` Rob Landley
2009-02-12 21:44       ` Rob Landley
2009-02-09 12:43 ` Mark McLoughlin
2009-02-09 21:36   ` Anthony Liguori [this message]
2009-02-10  0:47   ` Rob Landley
2009-02-10  7:22     ` M. Warner Losh
2009-02-13  8:40 ` Riku Voipio
2009-02-13  9:59   ` Stefano Stabellini
2009-02-13 16:30   ` Jamie Lokier
2009-02-13 17:00     ` Anthony Liguori
2009-02-13 19:04       ` [Qemu-devel] [PATCH] Revert block-qcow2.c to kvm-72 version due to corruption reports Jamie Lokier
2009-02-14 22:23         ` Dor Laor
2009-02-15  2:20           ` Jamie Lokier
2009-02-14 23:13         ` Anthony Liguori
2009-02-15  2:01           ` Jamie Lokier
2009-02-15  4:09             ` Anthony Liguori
2009-02-15 15:42               ` Jamie Lokier
2009-02-15 18:19                 ` Anthony Liguori
2009-02-15 18:34                   ` Johannes Schindelin
2009-02-16  1:01                     ` Anthony Liguori
2009-02-17  0:52                       ` Jamie Lokier
2009-02-17  2:55                         ` Anthony Liguori
2009-02-16  1:19                     ` Anthony Liguori
2009-02-17  1:01                   ` Jamie Lokier

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=4990A1E5.8050809@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=markmc@redhat.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).