From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [ANNOUNCE] QEMU 2.1.0 is now available
Date: Mon, 4 Aug 2014 14:56:36 +0200 [thread overview]
Message-ID: <20140804125636.GA17144@redhat.com> (raw)
In-Reply-To: <CAFEAcA_ChuX8AKq8-SuMjgOoJ_Fo0j1CgY=Ts11snaMjdSE2wQ@mail.gmail.com>
On Fri, Aug 01, 2014 at 11:33:28PM +0100, Peter Maydell wrote:
> On 1 August 2014 17:41, Michael Roth <mdroth@linux.vnet.ibm.com> wrote:
> > On behalf of the QEMU Team, I'd like to announce the availability of
> > the QEMU 2.1.0 release. This release contains 2200+ commits from 180
> > authors.
>
> > Thank you to everyone involved!
>
> Yep, thanks to everybody who helped get this one out of the door;
> trunk is now re-opened for 2.2 development.
>
> If there's anything you think we should maybe try to do better or
> differently next time round, now might be a good time to suggest it.
> Personally I think it went reasonably well and I was happy with the
> length of hardfreeze time. We should remember to ask for updates
> of the message translations at rc0/rc1 time rather than having them
> appear very late in the cycle, perhaps.
>
> thanks
> -- PMM
I agree, if went well.
I already have some bugfix patches which would be
preferable on a stable branch rather than
make them wait for 2.2.
How about we schedule periodic 2.1.y updates?
I think this has a better chance to work than
the "whenever we feel this is a good idea" model
we tried previously.
--
MST
next prev parent reply other threads:[~2014-08-04 12:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 16:41 [Qemu-devel] [ANNOUNCE] QEMU 2.1.0 is now available Michael Roth
2014-08-01 22:33 ` Peter Maydell
2014-08-04 9:50 ` Kevin Wolf
2014-08-04 12:56 ` Michael S. Tsirkin [this message]
2014-08-04 13:21 ` Mark Cave-Ayland
2014-08-04 13:37 ` Peter Maydell
[not found] ` <53E03454.9060103@netapp.com>
2014-08-05 9:47 ` Michael S. Tsirkin
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=20140804125636.GA17144@redhat.com \
--to=mst@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--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 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.