From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: Richard Henderson <richard.henderson@linaro.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: proposed 7.1 release schedule
Date: Mon, 23 May 2022 10:53:44 +0100 [thread overview]
Message-ID: <CAFEAcA80ABJ+RXFeoH4mo5yJk5oNh4Zc5QTBN35vVOL4eg0cNQ@mail.gmail.com> (raw)
I just put some proposed dates into the 7.1 schedule page:
https://wiki.qemu.org/Planning/7.1#Release_Schedule
* 2022-07-12 Softfreeze
* 2022-07-19 Hardfreeze. Tag rc0
* 2022-07-26 Tag rc1
* 2022-08-02 Tag rc2
* 2022-08-09 Tag rc3
* 2022-08-16 Release; or tag rc4 if needed
* 2022-08-23 Release if we needed an rc4
Does this work for people? I just worked backwards
from a final release date about 4 months after 7.0; easy
enough to shift it forward or back by a week or so if
that works better for some reason.
thanks
-- PMM
next reply other threads:[~2022-05-23 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 9:53 Peter Maydell [this message]
2022-05-23 13:20 ` proposed 7.1 release schedule Stefan Hajnoczi
2022-05-23 15:08 ` Richard Henderson
2022-05-23 19:29 ` Peter Maydell
2022-06-20 10:50 ` Peter Maydell
2022-06-20 14:28 ` Richard Henderson
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=CAFEAcA80ABJ+RXFeoH4mo5yJk5oNh4Zc5QTBN35vVOL4eg0cNQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).