WeeklyTelcon_20200602

Open MPI Weekly Telecon ---

Will we want a v4.0.4rc3?
- Took a low-risk bugfix after rc2.
- Do we do an rc3 just for this low-risk fix?
- Maybe do an rc3 with expectation that if no issues in 24 hours, we'll ship release.
v4.0.4rc2 - Announced this week. Asking for people to test for feedback
Given the v4.1 plan (see below), we'd like to release v4.0.4 before next Tuesday.

PMIX
- New Blocker Found:
- generate PPN scaling issue - simple algorithmic issue in this function
Schedule:
- PRRTE - Intel is changing his priority to move PRRTE to low priority. - Intel needs it by Q4, but end of summer at the latest. - It works with tiny option set. - Many feature requests. Many CI options.
- PRRTE changes should not block OMPI from branching, as it's a simple submodule update.
We went through a number of PRRTE defects, listed on v5.0 spreadsheet.
- Can't ship OMPI v5.0 by the end of July.
- Amazon needs a release to deliver multi-nic OFI features
  - Also needs collectives components updates.
  - Maybe tuning update PR, maybe more?
  - Maybe George's new collectives component on v4.1
- This would open it up to other stakeholders who need a feature (waiting on v5.x for feature)
  - v5.0 probably won't make end of summer. If you're waiting on v5.0 would a v4.1 be acceptable?
  - a v4.1 release, couldn't
  - If the branching is delayed significantly, can revisit some of the v5.0 feature list.
What if we try to do a more minimal v5.0 that addresses AMAZON's needs?
- Worried that a bad prrte will damage Open-MPI brand badly.

What would be release target for v4.1?
- AWS would push for end of June release.
- Lets just say we're going to do this.
NOT touching runtime!!!
Anyone have objections to v4.1?
- Send out email on devel-core.
- Branch from v4.0.4
AWS can be release manager for v4.1
- Need a 2nd release manager, discuss next week.
- Get list of things people are trying to push in.
- Plan on commiting
Time to branch: by next Tuesday.
Brian will email devel-core with summary of discussion.