Page History

...

This presentation by Eric Barton (from SC10) elaborates on these themes.

Landing a

...

Feature to a

...

Community Release

The community

Intel produces maintenance releases every 3 months. Check the Community Lustre Roadmap to find out when the next one is scheduled and which version of Lustre it will be against.

Note that landings for the release will freeze a month prior to GA to ensure sufficient time to do large-scale stress testing, performance benchmarking, and interoperability testing.

Patch Landing Checklist

1. A JIRA ticket has been opened to track the issue
2. Test and commit your patch locally using acceptance-small.sh
3. The patch follows the Requirements for patch submission:
   1. The Commit Comments are well formatted and useful
   2. Verify patch follows Lustre Coding Guidelines (at least "git show | contrib/scripts/checkpatch.pl -" passes)
   3. A regression test has been created that fails without the patch and passes with the patch
   4. The patch has the appropriate signed off by line
4. The patch has been uploaded to Gerrit
5. Request at least two Patch Inspection approvals (preferably ones with experience in this area of code) on the Gerrit change
6. Record the Gerrit change URL in the Jira ticket
7. Additional test results appropriate for the patch being landed (interoperability, performance, etc) should be attached to the Jira ticket.
8. Once Maloo has reported the tests all pass, add Gerrit Gatekeeper as inspector on the patch to notify him/her that the patch is ready to be merged
9. The branch gatekeeper will review the patch, confirm the test results, and submit it when everything goes well
10. If the submission failed due to patch conflict(s), the gatekeeper will ask you to rebase your patch with the target branch and repeat above steps.
11. If your patch is needed for other branch(es), please repeat above steps against corresponding branch(es).

Landing a Feature to a Feature Release

Intel produces feature releases every 6 months. Check the Community Lustre Roadmap to find out when the next one is scheduled. At the beginning of the development cycle, the features that will be included into the upcoming release are decided, and a landing schedule is worked out to ensure that not all of the features try to land in the week before the code freeze. The feature code freeze may be as early as 3 months prior to the release date, depending on the number and scope of features that are to be landed.

...

If you are unable to find a match, then open a new JIRA ticket outlining your plans, including the intended purpose of the development and any initial thoughts on design. Then, mail the lustre-devel mailing list to draw attention to the ticket. This will alert Intel and other alert other community members of your intentions and may well result in potential collaborators stepping forward.

...

It is also strongly suggested that you gain experience in the Lustre landing process by fixing one or more bugs for a maintenance release before attempting to tackle writing a Lustre feature. Feel free to ask for suggestions on the lustre-devel mailing list for a suitable bug to get started with.

Schedule and Timing

Intel Community Lustre releases operate to a "train model". The schedule is fixed and will not wait for features that are not ready in time - they are deferred to the next release.

...

Seeking Guidance

Please alert the Intel team community via the lustre-devel mailing list if you need some extra guidance in getting your patch submitted for the release.