From: Julien Grall <julien.grall@linaro.org>
To: xen-devel <xen-devel@lists.xenproject.org>
Cc: Lars Kurth <lars.kurth@citrix.com>,
"committers@xenproject.org" <committers@xenproject.org>
Subject: Re: Xen 4.10 Development update: code freeze date
Date: Tue, 10 Oct 2017 17:58:57 +0100 [thread overview]
Message-ID: <36658b11-60a8-4ffd-5752-74532f4508d8@linaro.org> (raw)
In-Reply-To: <31dd9922-356e-0618-b34e-ecd43e3848ce@arm.com>
Hi all,
Quick reminder, the code freeze is tomorrow (Wednesday).
Please check-in everything by end of the day tomorrow. An RC will be cut
on we get a push.
Cheers,
On 26/09/17 16:22, Julien Grall wrote:
> Hi all,
>
> The hard code freeze date will be extended by a week and half. I still
> expect Xen 4.10 released on time.
>
> The new schedule is:
> * Code freeze: October 11th, 2017
> * RC1: TBD
> * Release: December 2nd, 2017
>
> Note that the last posting date has already past. All new series posted
> will be queued for the next release.
>
> Cheers,
>
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-10-10 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 15:22 Xen 4.10 Development update: code freeze date Julien Grall
2017-10-10 16:58 ` Julien Grall [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=36658b11-60a8-4ffd-5752-74532f4508d8@linaro.org \
--to=julien.grall@linaro.org \
--cc=committers@xenproject.org \
--cc=lars.kurth@citrix.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 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).