From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] Any QEMU 2.8 release blockers?
Date: Tue, 13 Dec 2016 15:33:40 -0600 [thread overview]
Message-ID: <20161213213340.5009.90101@loki> (raw)
In-Reply-To: <CAJSP0QUkFjfsQ21i3-qXQL5N3xJd6WnEmy1BewMV3z=VOpr7BQ@mail.gmail.com>
Quoting Stefan Hajnoczi (2016-12-13 15:04:24)
> On Tue, Dec 13, 2016 at 10:01 AM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> > On Fri, Dec 9, 2016 at 3:34 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> >> Hi folks,
> >> How is QEMU 2.8.0-rc3 holding up?
> >>
> >> I'm not aware of release blockers. QEMU 2.8.0 will be released on
> >> Tuesday, December 13th if nothing comes up. It will be the -rc3
> >> source tree.
> >
> > There have been no release blockers so I plan to tag QEMU 2.8.0 today
> > (December 13th at 19:00 UTC).
> >
> > If something critical turns up please notify me on IRC (stefanha on
> > #qemu irc.oftc.net).
>
> Mike Roth discovered a migration compatibility bug introduced by
> commit d1b4259f1ab18af24e6a297edb6a8f71691f3256 ("virtio-bus: Plug
> devices after features are negotiated"). The release will be delayed
> until this is resolved.
>
> Please check the mailing list for discussion. Mike is sending out a
> mail summarizing the bug.
I've posted a summary in the original patch thread:
https://lists.gnu.org/archive/html/qemu-devel/2016-12/msg01862.html
>
> Stefan
>
next prev parent reply other threads:[~2016-12-13 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 15:34 [Qemu-devel] Any QEMU 2.8 release blockers? Stefan Hajnoczi
2016-12-13 10:01 ` Stefan Hajnoczi
2016-12-13 21:04 ` Stefan Hajnoczi
2016-12-13 21:33 ` Michael Roth [this message]
2016-12-13 21:39 ` Stefan Weil
2016-12-13 21:52 ` Stefan Hajnoczi
2016-12-14 6:31 ` [Qemu-devel] QEMU po files / translations (was: Any QEMU 2.8 release blockers?) Stefan Weil
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=20161213213340.5009.90101@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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.