From: Jan Beulich <jbeulich@suse.com>
To: "Oleksii K." <oleksii.kurochko@gmail.com>
Cc: committers@xenproject.org, community.manager@xenproject.org,
Kelly Choi <kelly.choi@cloud.com>,
xen-devel@lists.xenproject.org
Subject: Re: Code freeze date for Xen 4.19 is 31.05.2024
Date: Mon, 27 May 2024 17:55:25 +0200 [thread overview]
Message-ID: <2d0c1ebf-fecd-43a5-b616-9869e98ece5e@suse.com> (raw)
In-Reply-To: <48f5e40e1f13ef96e8448b59f76878b522876030.camel@gmail.com>
On 27.05.2024 17:52, Oleksii K. wrote:
> On Mon, 2024-05-27 at 17:12 +0200, Jan Beulich wrote:
>> On 27.05.2024 15:58, Oleksii K. wrote:
>>> I would like to remind you that the code freeze date for Xen 4.19
>>> is
>>> May 31, 2024.
>>
>> I may be confused: With feature freeze having been last Friday aiui,
>> isn't
>> this a little too short a period? I was actually expecting a longer-
>> than-
>> normal one to account for the Xen Summit week.
> It makes sense to move the last day to June 14. Consequently, we would
> need to adjust the schedule as follows:
>
> Hard Code Freeze: from June 21 to June 28
> Final commits: from July 5 to July 12
> Release: July 17
>
> And this schedule also looks good to me.
>
> However, another option is to combine the Code Freeze and Hard Code
> Freeze periods since both phases are about accepting only bug fixes,
> differing only in the severity of the fixes.
I'm okay with whichever way you want it. All I'm seeking is clarity.
Jan
next prev parent reply other threads:[~2024-05-27 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 13:58 Code freeze date for Xen 4.19 is 31.05.2024 Oleksii K.
2024-05-27 15:12 ` Jan Beulich
2024-05-27 15:52 ` Oleksii K.
2024-05-27 15:55 ` Jan Beulich [this message]
2024-05-27 16:09 ` Oleksii K.
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=2d0c1ebf-fecd-43a5-b616-9869e98ece5e@suse.com \
--to=jbeulich@suse.com \
--cc=committers@xenproject.org \
--cc=community.manager@xenproject.org \
--cc=kelly.choi@cloud.com \
--cc=oleksii.kurochko@gmail.com \
--cc=xen-devel@lists.xenproject.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.