[ofiwg] 01/07/2025 OFIWG Meeting Notes

[Ingerson, Alexia]

01/07/2025
Participants:
Alexia Ingerson (Intel)
Jianxin Xiong (Intel)
Bob Cernohous (Cornelis)
Charles Sherada (Cornelis)
Howard Pritchard (LANL)
Ian Ziemba (HPE)
Jerome Soumagne (HPE)
Juee  Desai (Intel)
Rajalaxmi Angadi (Intel)
Shi Jin (AWS)
Stephen Oost (Intel)
Steve Welch (HPE)
Zach Dworkin (Intel)

Summary:
Proposal to release feature releases less frequently. AWS, Cornelis, and HPE would like to stay more frequent. We will keep the current schedule (3 feature releases in March, July, and November with a  few bug fix releases) at least for this year and maybe revisit release cadence.
New Intel security update requires author of PRs to be in OFIWG organization in order to run and pass. If you have anyone in your organization that needs to be a part of the organization to submit PRs, let Jianxin know.
Mail list server issue reported last meeting has resolved itself.

Notes:
Release cadence:

  *   Consider reducing number of releases per year (feature releases are underutilized)
     *   Current: 3 feature releases (March, July, November) + a few bug fix releases
     *   Proposal 1: 2 feature releases (May/November) + a few bug fix releases
     *   Proposal 2: Bug fix releases in March/July, feature release in November
  *   Q: AWS is preparing feature targeted for Q1, feature release in first half would be nice.
  *   Does AWS need more frequent releases?
  *   AWS releases quarterly on separate branch, would like to have feature release in March
  *   Q: What are other companies' release cadences
  *   Cornelis: more difficult if upstream releases are less frequent since then Cornelis releases don't match with libfabric release and just random commit id
  *   For now, stick with the current schedule.
  *   For HPE: they also have ways to release from outside of release cadence but would prefer more often
  *   Q: Do we have to have one release manager? Other projects have multiple ones. Would it help to have more from other companies?
  *   Not about the burden, we have two people helping. Wondering if the release cadence is utilized or under utilized.
Intel CI change

  *   Security measure added to CI. Major change is that if PR author is not part of OFIWG  organization, will fail. Need invitation to join and trigger CI.
  *   If anyone in your organization needs an invitation, let Jianxin know and he can add them.
Mail list server issue update

  *   List server issue was reported last time, seems to have resolved itself


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofiwg/attachments/20250107/b5fc35bc/attachment-0001.htm>