CDWG Minutes 2013-07-03

From OpenSFS Wiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.


Agenda

  • Report on completion of 2.5 scoping effort (Chris)
  • Discussion and final decision on changing the official, community announced, "scheduled maintenance release" branch from 2.4 to 2.5.
  • Discuss applying CC-BY-SA to wiki and/or lustre portal

Attendance

  • Chris Morrone (LLNL)
  • Megan (Xyratex)
  • Kevin?
  • Nic Henke (Xyratex)
  • IU
  • Brett Costolo (Intel)
  • John
  • Cory Spitz (Cray)
  • Peter Jones (Intel)


Minutes

2.5.0 Scoping

Make 2.5 "scheduled maintenance release"

All in agreement to advertise the change to 2.5 as the "scheduled maintenance release" branch.

No objections.

Some discussion about how we will communicate and decide on future branches. Cory asked if we can expect Intel to continue to be as accommodating to the community's wishes in the future.

Peter pointed out that we are all serving the same, or similar markets. (So it is likely that we will be able to align on common goals.)

We just need to keep our lines of communication open, and coordinate our goals for lustre.

Apply CC-BY-SA to wiki

No objections.

Other

HSM Status

Cory: Is HSM going to be ready?

Work is under way. 11 patches under review, possibly a couple nearing review. Work is progressing, and we'll see where we are in a couple of weeks.

What can we do to help with 2.5.0?

Testing!

Work on your patches _now_, don't wait for the end of the development cycle.

Pitch in on fixing bugs.

SLES11SP3 Clinet Support for 2.5.0

Cory reports that SLES11SP3 has been released. Asked if it can add _client_ support. Peter suggested that we can apply same criterion as RHEL7: we can add support if it distro is released sufficiently in advance of the code freeze.

All agreed it sounds reasonable to add client support for SLES11SP3.

Action Items

  • Update roadmap to reflect change from 2.4 to 2.5
  • After roadmap update, send email announcement of change