Release 2.11.0

From Lustre Wiki
Revision as of 16:22, 13 July 2017 by Jgmitter (talk | contribs)
Jump to navigation Jump to search

Current Schedule

  • Oct 15 2017 - Feature Freeze (open for features July x 2017)
  • Dec 31 2017 - Code Freeze
  • Jan 31 2018 - Release 2.11.0

(Note: these are very rough guidelines. For more accurate details on the schedule please refer to LWG call minutes)

Scope

Test Matrix

  • Servers: RHEL 7.4
  • Clients RHEL 7.4, SLES 12 SP3, Ubuntu 16.04
  • OFED: inkernel
  • E2FSProgs: v1.42.13.wc5
  • Interoperability: Latest 2.10.X Servers/Clients

Features

The following features are under active development and could be possible for landing during the 2.11 release cycle

Feature Developers Reviewers Testers Docs Confirmed in 2.11
Lock Ahead Patrick Farrell Vitaly Fertman Justin Miller Patrick Farrell, LUDOC-379 Not Yet
Data on MDT Mike Pershin Niu Yawei, Jinshan Xiong TBD TBD Not Yet
FLR - Delayed Resync Jinshan Xiong Mike Pershin, Bobijam Xu TBD TBD Not Yet

General Work and Maintenance

From the Lustre project page in the Lustre issue tracker, we can see a dashboard for the project. On that page under the "Versions: Unreleased" section, there are links to future releases and all of the issues that are either targeted to be addressed in that release, or are already addressed for the release. Here is a shortcut to Lustre 2.11.0's issue summary page:

 Lustre 2.11.0 Issues

Any issue that contains "Lustre 2.10.0" in the "Fix Version/s" field of a ticket is intended to be fixed for version 2.11.0. The Lustre 2.11.0 Issues list is fluid, and will be updated on a continual basis as resources and priorities change.

If you would like to own one or more tasks for the release but are not currently listed in the drop-down list of developers in JIRA then please email Peter Jones to get that setup

A convenience search filter is supplied for anyone looking for work that needs to be done for 2.11.0:

 Lustre 2.11.0 Unassigned Issues

In addition, a search filter is available for anyone looking to start Lustre development with some simple development tasks, or anyone with a few minutes/hours available to improve Lustre:

 Lustre easy-to-fix issues