qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: proposed 7.1 release schedule
Date: Mon, 20 Jun 2022 07:28:07 -0700	[thread overview]
Message-ID: <41e54f7f-317d-79bd-ca91-a67e8ba6a721@linaro.org> (raw)
In-Reply-To: <CAFEAcA_LzYqxSe=Pa7KJg-GuR8_E=Qfjj0s1by9LMasRiUR9sA@mail.gmail.com>

On 6/20/22 03:50, Peter Maydell wrote:
> On Mon, 23 May 2022 at 16:08, Richard Henderson
> <richard.henderson@linaro.org> wrote:
>>
>> On 5/23/22 02:53, Peter Maydell wrote:
>>> 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.
>>
>> Shifting later a week or so would be better. I'm on holiday from 13-22 July -- unless
>> someone would like to manage merges in that period?
> 
> I've updated the wiki page to move the dates all one week
> later, and removed the "tentative" label.

Thanks.

> Ping me when we get closer to your holiday to remind
> me that I agreed to do merges then :-)

Will do.  :-)


r~



      reply	other threads:[~2022-06-20 14:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23  9:53 proposed 7.1 release schedule Peter Maydell
2022-05-23 13:20 ` 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 [this message]

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=41e54f7f-317d-79bd-ca91-a67e8ba6a721@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=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).