Landing a Patch to a Maintenance Release

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

Note that landings for the release will freeze a month prior to GA.

Pre-requisites

Before getting started please read over the background material on Patch Landing Process, Signed Off By, Uploading Patches to Gerrit and Requirements for Patch Submission

Checklist

1. All code conforms to the Coding Guidelines
2. A JIRA ticket has been opened to track the issue
3. The commit comment is well formatted
4. A regression test has been created that fails without the patch and passes with the patch
5. The patch has been uploaded to Gerrit with the appropriate signed off by line

Landing a Patch to a Feature Release

Whamcloud produces feature releases every 6 months. Check the Whamcloud Lustre Roadmap to find out when the next one is scheduled.

First Steps

Before starting to think about the logistics associated with developing your feature it is imperative to share your plans with the Lustre community. Otherwise you may find that you are either duplicating work with someone else or that your work needs to be repeated to accommodate some other changes occurring in the same part of Lustre code.

More soon...

Seeking Guidance

Please alert the Whamcloud team via the wc-discuss mailing list if you need some extra guidance in getting your patch submitted for the release.