From: Christopher J. Morrone <morrone2@llnl.gov>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] Lustre 2.9 planning and Projects page
Date: Tue, 08 Sep 2015 16:57:41 -0700 [thread overview]
Message-ID: <55EF75F5.70206@llnl.gov> (raw)
Hello everyone,
With Lustre 2.8 nearing completion, it is a good time for everyone to
communicate their intentions for major changes that they intend to try
to complete in time for 2.9.
Not everything we had hoped to land for 2.8 was able to run the complete
peer review process and land before the Feature Freeze or Code Freeze
windows closed. Those changes that missed the 2.8 landing windows are,
at this time, the closest to being ready for landing during the 2.9
landing windows.
Keep in mind that major changes and features that you want to get into
Lustre are more likely to land smoothly if you discuss your intentions
and design details here on the lustre-devel mailing list well in advance
of the target landing date that you have in mind. Peer review of
designs is as important as peer review of code. If your peers have
approved your design ahead code submission time, even informally, then
the code review process is likely to go much more smoothly.
Also, for any change reasonably large in size (e.g. new features, major
code refactorings), it is wise to list your under-way project on the
lustre.org wiki's Projects page:
http://wiki.lustre.org/Projects
Keeping your project entry and its target completion date current will
help us all know what other work is going on in parallel that might
impact our own projects.
Chris
reply other threads:[~2015-09-08 23:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=55EF75F5.70206@llnl.gov \
--to=morrone2@llnl.gov \
--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.