WeeklyTelcon_20170912

Open MPI Weekly Telcon

Going to switch v2.0.x to only Critical fixes only!
- Only Critical fix we know of now is MAdvise fix.
Ask people to move to v2.1.x or v3.0.0

Cisco is doing a lot of testing, and even more failures on master.
- procs not able to reach each other.
- some failures to launch, etc.
- Think it's https://github.com/open-mpi/ompi/issues/4131
NFS path testing - Annoying check in opal, and associated test.
- Problem was too many buffers to
Brian is going to add -m32 builds to our test suite.
- But not actually IA32 hardware, but close enough.
Brian tried some new ways of building the tarball, but it failed... so dealyed until Thanksgiving.
Root filesystem on webserver failed, because jenkins failed.
- Jenkins reachout plugin is terrible, so having the clients reach out to the server is more stable.
- Brain

Schedule for NEXT v3.1 release (Branch and Ship)
- Would like to have all features into master before we branch for v3.1
- Ralph is working on tool connection.
- No whitelist for v3.1. v3.0.0 was transition, and no more whitelists.
Ralph proposed to have a bot that could scan issues, and close issues if no action in some time.
- A bit of concern about auto-closing (losing visibility of legitimate issues)
- Ticket shaming seems to work.
Brian wrote a histogram for reporting the number of compiler warnings found in make dist_check:
- https://jenkins.open-mpi.org/jenkins/job/open-mpi.build.distcheck/
- This brings visibility to this, and we'd like to drive this number down over time.