Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: update URLs for roadmap, mailing list, and downloads

...

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.

...

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 hpddlustre-discuss devel mailing list to draw attention to the ticket. This will alert Intel and 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 hpddlustre-discuss devel mailing list for a suitable bug to get started with.

...

For a feature release scheduled for release in month T the schedule is roughly as follows. For more precise dates, keep up to date on the hpddlustre-discuss devel mailing list .

  1. T-7 A call for features is sent out to the hpddlustre-discuss devel mailing list. The amount of change that can be landed for a given release is limited so it is prudent to respond early if you feel that you will have a feature that warrants consideration for inclusion. Expect to be asked to provide the information on the Feature Landing Checklist below - either completed or with estimates as to when any missing portions will be completed. Typically, feature development is already well underway before a feature is scheduled for landing.
  2. T-6 Initial review of candidate features to define the scope of the release. A test plan is created and the Community Lustre Roadmap is updated. A landing schedule is created so that feature landings are spaced out to make it easier for intermediate testing to identify when features introduce regressions. If serious regressions are found when a feature is landed then it will be reverted from master until the problems have been addressed. It should be obvious that not all changes can land in the last weeks before the feature freeze, hence the requirement that features already be close to completion before scheduling them for landing.
  3. T-3 Feature Freeze - feature landing is finished, bug fixes only from now on. The Community Lustre Roadmap is updated.
  4. T-1 Code Freeze - critical bug fixes only from now on. A release candidate (RC) is tagged and release testing commences
  5. T0 GA announced and RPMs available for download from the Intel download site

Feature Landing Checklist

...

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