From: "Andreas Färber" <afaerber@suse.de>
To: "Justin M. Forbes" <jmforbes@linuxtx.org>
Cc: Markus Armbruster <armbru@redhat.com>,
Alon Levy <alevy@redhat.com>,
qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] Qemu stable releases
Date: Fri, 09 Dec 2011 13:55:34 +0100 [thread overview]
Message-ID: <4EE20546.5000601@suse.de> (raw)
In-Reply-To: <1323115683.6884.8.camel@fedora64.linuxtx.org>
Am 05.12.2011 21:08, schrieb Justin M. Forbes:
> Typically I get a flurry of patches shortly after
> a release (and they have already started for 1.0). I have tried to get
> a .1 release out in a timely manner, and then it seems patches for
> stable become few and far between. In the 0.14 and 0.15 series, not
> even enough to warrant a .2 release. Perhaps this is due to lack fixed
> issues, or lack of effort to submit to stable.
> 3) Security fixes do not follow this schedule, and will trigger a stable
> release as needed.
I would've thought that the usb-ccid CVE alone warrants a 0.15.2 of qemu
and qemu-kvm. I am surprised nothing has happened there yet...
http://patchwork.ozlabs.org/patch/128064/
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:[~2011-12-09 12:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 20:08 [Qemu-devel] Qemu stable releases Justin M. Forbes
2011-12-06 9:27 ` Stefan Hajnoczi
2011-12-09 10:39 ` Richard W.M. Jones
2011-12-09 12:01 ` Richard W.M. Jones
2011-12-09 13:25 ` Anthony Liguori
2011-12-09 13:47 ` Richard W.M. Jones
2011-12-09 12:55 ` Andreas Färber [this message]
2011-12-09 13:24 ` Anthony Liguori
2011-12-09 13:50 ` Andreas Färber
2011-12-09 13:28 ` Justin M. Forbes
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=4EE20546.5000601@suse.de \
--to=afaerber@suse.de \
--cc=alevy@redhat.com \
--cc=armbru@redhat.com \
--cc=jmforbes@linuxtx.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 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.