SHORT VERSION Per Dallas discussions:
* We're looking to release v2.1.0 by 31 Oct * Feature freeze / cutoff is 30 Sep * There are "must have" items that will block the release schedule If we really want a release by 31 Oct, there is much work to do in a short amount of time. MORE DETAIL Per our Dallas discussions (https://github.com/open-mpi/ompi/wiki/Meeting-2016-08 and https://github.com/open-mpi/ompi/wiki/Meeting-Minutes-2016-08), we are looking to release v2.1.0 by the end of October. We had talked about September 30 as the feature freeze date for v2.1.0. This is rapidly approaching. According to https://github.com/open-mpi/ompi/wiki/Releasev2x, here are the remaining incomplete v2.1.0 "must have's": * PMIx 2.0 integration (Intel, MLNX) - partially in master Issue #2072<https://github.com/open-mpi/ompi/issues/2072>. Will require porting to the v2.x branch. * Open SHMEM 1.3 compliance issue #2109 tracking multiple PRs<https://github.com/open-mpi/ompi/issues/2109> * mpool/rcache rewrite (LANL) - already in master * HCOLL datatypes - already in master * Better CMA support detection / make CMA the default in vader PR #1306<https://github.com/open-mpi/ompi-release/pull/1306> Other new features can be accepted to v2.1.0, but not after 30 Sep. Additionally, there are currently 6 blocker issues: https://github.com/open-mpi/ompi/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20milestone%3Av2.1.0%20label%3Ablocker<https://github.com/open-mpi/ompi/issues?utf8=✓&q=is:issue%20is:open%20milestone:v2.1.0%20label:blocker> in various states (some haven't started, some are partially complete, some are all-but-complete). These, too, must be fixed before release, and may delay the release. -- Jeff Squyres jsquy...@cisco.com<mailto:jsquy...@cisco.com> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ devel mailing list devel@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
