From: Patrick Farrell <paf@cray.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] DNE2 feature patch landing
Date: Thu, 2 Jul 2015 14:36:40 -0500 [thread overview]
Message-ID: <559592C8.2090905@cray.com> (raw)
In-Reply-To: <1435865147.2548.26.camel@intel.com>
Speaking for myself (IE, not on behalf of my employer), strongly
endorsed. While the feature freeze is important, there's a good reason
for the slight slippage here, and this is an important feature. I have
no issue with slight slippage as long as a serious, good faith effort
was made with a realistic plan to hit the cutoff, as I think is the case
here.
- Patrick
On 07/02/2015 02:25 PM, Henwood, Richard wrote:
> All,
>
> Last week a patch landed conflicting with the DNE2 project that was
> preparing to land for 2.8:
> http://wiki.lustre.org/Projects
>
> The DNE2 feature patches were rapidly re-based, re-reviewed and prepared
> again for landing. However, a unrelated test failure from the continuous
> integration environment has delayed the landing of these three patches
> beyond the feature freeze date of June 30th.
>
> We anticipate that it would only take an extra day or two to get the
> outstanding DNE2 patches landed and recommend that we extend the feature
> freeze for these to allow this OpenSFS-funded project to complete. We
> do not expect this to have a material affect on the 2.8 release date.
>
> I'm asking the list now for a couple of supporting community voices to
> endorse this request.
>
> best regards,
> Richard
next prev parent reply other threads:[~2015-07-02 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 19:25 [lustre-devel] DNE2 feature patch landing Henwood, Richard
2015-07-02 19:36 ` Patrick Farrell [this message]
2015-07-02 20:46 ` Simmons, James A.
2015-07-02 20:58 ` Christopher J. Morrone
2015-07-06 14:46 ` Henwood, Richard
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=559592C8.2090905@cray.com \
--to=paf@cray.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.