From: Jones, Peter A <peter.a.jones@intel.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] Community Release Update
Date: Fri, 17 Jun 2016 00:18:45 +0000 [thread overview]
Message-ID: <D38889B6.D05AE%peter.a.jones@intel.com> (raw)
In-Reply-To: <D2DF7987.BC02C%peter.a.jones@intel.com>
Hi there
Apologies for the long overdue update but I wanted to formally let everyone know that the 2.9 feature freeze is in effect and we are in the stabilization period for the release. You can see the details of the features that made it in time on http://wiki.lustre.org/Release_2.9.0 . There still may also be some further enhancements to the builds to come ? Chris Morrone and others have been beavering away there. However, from a runtime point of view, the core content is in place and we will be focusing on hardening it ahead of a GA (which is targeted for the end of August)
Although it is still some months out (tentatively September) until master opens for feature landings again, we?re already thinking ahead and there is a draft page to start collecting details of candidate features for the community 2.10 release - http://wiki.lustre.org/Release_2.10.0. Naturally the details of supported third party software will change as we get closer to the time and newer versions emerge but the existing ?latest and greatest? are there as placeholders and there are also details of features currently in the frame. Please add details of anything that you are working on that you would like to propose for consideration.
Regards
Peter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20160617/8aae3b48/attachment.htm>
prev parent reply other threads:[~2016-06-17 0:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 14:18 [lustre-devel] Community Release Update Jones, Peter A
2016-06-17 0:18 ` Jones, Peter A [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=D38889B6.D05AE%peter.a.jones@intel.com \
--to=peter.a.jones@intel.com \
--cc=lustre-devel@lists.lustre.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.