From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: michael.roth@amd.com, richard.henderson@linaro.org,
peter.maydell@linaro.org
Subject: Re: QEMU 7.2 release schedule
Date: Thu, 1 Sep 2022 15:08:47 -0300 [thread overview]
Message-ID: <c8393f90-1718-a2be-213b-2dcec6af7ed9@gmail.com> (raw)
In-Reply-To: <Yw59JU3ja/EU3HL6@fedora>
On 8/30/22 18:12, Stefan Hajnoczi wrote:
> Hi,
> Richard Henderson has tagged QEMU 7.1 and handed over to me for the 7.2
> release cycle. Thanks to Richard and Michael Roth their work on 7.1!
Are you going to handle the pull requests for this release cycle? I saw
that you've handled Thomas' PRs.
If that's the case I'll CC you in the PRs instead of Peter/Richard.
Thanks,
Daniel
>
> Please check the proposed release schedule and let me know if they fall
> on inconvenient dates:
> - 2022-08-30: Beginning of development phase
> - 2022-11-1: Soft feature freeze. Only bug fixes after this point. All feature changes must be already in a sub maintainer tree and all pull requests from submaintainers must have been sent to the list by this date.
> - 2022-11-8: Hard feature freeze. Tag rc0
> - 2022-11-15: Tag rc1
> - 2022-11-22: Tag rc2
> - 2022-11-29: Tag rc3
> - 2022-12-06: Release; or tag rc4 if needed
> - 2022-12-13: Release if we needed an rc4
>
> The release planning page is now available on the wiki:
> https://wiki.qemu.org/Planning/7.2
>
> The changelog has been created so you can add items when code is merged:
> https://wiki.qemu.org/ChangeLog/7.2
>
> Stefan
next prev parent reply other threads:[~2022-09-01 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 21:12 QEMU 7.2 release schedule Stefan Hajnoczi
2022-08-31 17:23 ` Richard Henderson
2022-09-01 18:08 ` Daniel Henrique Barboza [this message]
2022-09-01 19:40 ` Stefan Hajnoczi
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=c8393f90-1718-a2be-213b-2dcec6af7ed9@gmail.com \
--to=danielhb413@gmail.com \
--cc=michael.roth@amd.com \
--cc=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 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.