From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] release retrospective, next release timing, numbering
Date: Tue, 1 May 2018 13:48:35 +0100 [thread overview]
Message-ID: <CAFEAcA8PKvW2P717b=TAfHHz-GYTYFcW0Z-MLMkSHfsMDhZVbA@mail.gmail.com> (raw)
In-Reply-To: <20180501122436.GA14803@stefanha-x1.localdomain>
On 1 May 2018 at 13:24, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> On Fri, Apr 27, 2018 at 04:51:03PM +0100, Peter Maydell wrote:
>> (2) release timing:
>> * usual schedule would give us a next release mid-to-late August
>> * unless I can persuade Stefan to do the release management this
>> cycle we might need to wind that in by a couple of weeks so
>> it's definitely done by the middle of August, to avoid a clash
>> with a personal commitment
>
> I will be offline mid-August to mid-September, sorry. Someone else can
> volunteer to do the release.
I think the best approach is that we'll make sure the dates for
the release are set so it's definitely done by mid-August,
and we'll find a suitable volunteer to do the post-release
pull request handling for late August/September...
-- PMM
next prev parent reply other threads:[~2018-05-01 12:49 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 15:51 [Qemu-devel] release retrospective, next release timing, numbering Peter Maydell
2018-04-27 16:17 ` Thomas Huth
2018-04-27 16:24 ` Peter Maydell
2018-04-27 16:42 ` Thomas Huth
2018-04-30 10:06 ` Paolo Bonzini
2018-04-30 10:11 ` Peter Maydell
2018-05-02 11:58 ` Daniel P. Berrangé
2018-05-02 12:05 ` Peter Maydell
2018-05-03 9:33 ` Daniel P. Berrangé
2018-05-03 9:42 ` Thomas Huth
2018-05-03 9:45 ` Daniel P. Berrangé
2018-05-03 14:01 ` Cédric Le Goater
2018-05-03 14:16 ` Cédric Le Goater
2018-05-03 18:02 ` Stefan Hajnoczi
2018-05-03 18:50 ` Dr. David Alan Gilbert
2018-05-04 8:29 ` Stefan Hajnoczi
2018-05-04 5:29 ` Markus Armbruster
2018-05-04 8:16 ` Stefan Hajnoczi
2018-05-04 8:24 ` Peter Maydell
2018-04-27 19:01 ` Michal Suchánek
2018-04-29 14:56 ` Richard Henderson
2018-05-02 10:41 ` Laszlo Ersek
2018-05-02 11:51 ` Peter Maydell
2018-05-07 18:12 ` Michal Suchánek
2018-04-30 10:35 ` Daniel P. Berrangé
2018-05-02 7:29 ` Markus Armbruster
2018-05-02 8:16 ` Daniel P. Berrangé
2018-05-02 9:44 ` Cornelia Huck
2018-04-30 9:29 ` Cornelia Huck
2018-04-30 10:01 ` Peter Maydell
2018-04-30 10:33 ` Daniel P. Berrangé
2018-04-30 11:21 ` Cornelia Huck
2018-04-30 17:36 ` Thomas Huth
2018-05-02 7:33 ` Cornelia Huck
2018-05-02 7:43 ` Liviu Ionescu
2018-05-02 7:59 ` Daniel P. Berrangé
2018-05-02 8:02 ` Liviu Ionescu
2018-05-02 8:13 ` Thomas Huth
2018-05-02 9:03 ` Liviu Ionescu
2018-05-02 9:10 ` Daniel P. Berrangé
2018-05-28 9:24 ` Paolo Bonzini
2018-05-02 9:21 ` Cornelia Huck
2018-05-02 9:22 ` Thomas Huth
2018-05-02 8:26 ` Cornelia Huck
2018-05-04 17:34 ` Max Reitz
2018-05-02 7:44 ` Gerd Hoffmann
2018-05-02 8:02 ` Daniel P. Berrangé
2018-05-03 7:21 ` Stefan Hajnoczi
2018-05-03 9:07 ` Daniel P. Berrangé
2018-05-03 9:26 ` Cornelia Huck
2018-05-03 9:26 ` Peter Maydell
2018-05-03 9:31 ` Daniel P. Berrangé
2018-05-03 9:47 ` Thomas Huth
2018-05-03 13:43 ` Gerd Hoffmann
2018-05-03 14:06 ` Thomas Huth
2018-05-03 14:16 ` Daniel P. Berrangé
2018-05-07 13:38 ` Kashyap Chamarthy
2018-05-07 16:51 ` Thomas Huth
2018-05-03 14:16 ` Cornelia Huck
2018-05-04 13:20 ` Kevin Wolf
2018-05-04 13:53 ` Thomas Huth
2018-05-04 14:23 ` Kevin Wolf
2018-05-04 17:30 ` Richard Henderson
2018-05-07 5:33 ` Thomas Huth
2018-05-07 14:05 ` Kevin Wolf
2018-05-22 10:07 ` Peter Maydell
2018-06-01 11:57 ` Daniel P. Berrangé
2018-04-30 14:23 ` Greg Kurz
2018-04-30 14:30 ` Peter Maydell
2018-04-30 14:34 ` Daniel P. Berrangé
2018-05-03 1:04 ` David Gibson
2018-05-01 12:24 ` Stefan Hajnoczi
2018-05-01 12:48 ` Peter Maydell [this message]
2018-05-03 21:52 ` Laurent Vivier
2018-05-04 8:40 ` Stefan Hajnoczi
2018-05-28 5:31 ` Philippe Mathieu-Daudé
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='CAFEAcA8PKvW2P717b=TAfHHz-GYTYFcW0Z-MLMkSHfsMDhZVbA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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).