CDWG Minutes 2013-06-05

From OpenSFS
Jump to: navigation, search


Agenda

  • 2.4.0 commentary
  • 2.5 Development Planning

Attendance

  • Chris Morrone (LLNL)
  • James Simmons (ORNL)
  • Peter Jones (Intel)
  • Nic Henke (Xyratex)
  • Kevin Canady (Xyratex)
  • Cory Spitz (Cray)
  • Justing Miller (IU)
  • Kit Westneat (DDN)
  • Ashley Pitman (DDN)

Minutes

2.4.0 tag

2.4.0 released, congratulations all around.

Discussion about things we learned during 2.4 development cycle and would like to see improved in 2.5. Things we decided to work on captured in the 2.5.0 section of these notes.

2.5.0 Development Planning

What will we do with Fix Version / Affects Version

Fix Version field: Inital list of tickets with a tag decided during intial scoping effort, Intel triages, CDWG to susggest Intel adjustments

James - Give it the extra month, if HSM is done early, and 2.5 can be released early, fine.

James - people report on status of their own in-progress work regularly on CDWG calls

  • "Test matrix" - AKA "which distros do we support"
    • Need Decide on RHEL7 support. Set date by which RHEL7 must be released if it going to include support for it in 2.5.0
      • Consensus: Make a decision at the feature freeze point.

2.5.0 Scope

Chris - Imporant to scope work as completely as we can so we know throughout the development cycle if we are on target. We can make adjustments to scope much earlier if we know whether or not we are on target.

Peter - Important that the scope not allocate 100% of developer time, need to leave unallocated time to address bugs which come in on an unpredictable schedule.

Chris's suggested scoping areas for 2.5:

  • HSM
  • Cleanup unfinished 2.4 work (address technical debt)
  • Some subset of long ignore bugs (e.g. LU-7/LU-793) that never get fixed if left unscoped, and just "when there's time".
  • Client performance issues (not mentioned on phone)

Action Items

  • Chris to start wiki page explaining usage of "Fix Version/s" field, and how we scope work for a release
  • Chris to start a calendar of Lustre development dates: Deadline for initial scoping effort, Feature Freeze, Code Freeze, Release date
  • Retire "Community Development In Progress" wiki page.
    • Intially add links noting that it is being deprecated in the near furture
    • When "Fix Version/s" field is applied to intial scope of work for 2.5, change it to point to the list of unresolved 2.5 work in Jira
  • Complete intial 2.5 scoping effort by June 14