-
Notifications
You must be signed in to change notification settings - Fork 860
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v3.0.0 feature whitelist #3107
Comments
The Hook framework was merged into |
The get/set Info stuff is very close, passed review, and just needs a rebase: PR #2941. |
We will delay #2941 and hwloc removal to a future release. |
@jladd-mlnx where are we with these UCX related features? |
UCX multi-threading PR should be posted for master by end of this week according to @jladd-mlnx |
@hppritcha Done PR: #3168 |
At this point, I would suggest we plan on defaulting back to the PMIx v1.2 and the code on the existing 3.x branch. I'm getting very little help on PMIx right now, and no help at all on the other issues still lingering for 3.0. Given that we are near the end of April, I see little to no prospect of this being done in time for a June release. |
Thanks for the update Ralph! Going with v1.2 sounds like the right thing to do at this point. |
Yeah, I think so. However, note that it seems highly unlikely that 3.0 can be released in June. For example, I see only one MTT test being run on the 3.x branch (yours, and it even failed one of its builds) |
I'd really like to find some way to make this work. I'm talking with our PMIx developers to see if there is something we can do in this timeframe. |
We've pulled all the whitelist items into 3.0 and are back to bugfix only, so closing this ticket. |
Per the 2/28/17 devel core minutes the following items made it to the v3.0.0 feature whitelist:
Removing Internal hwloc component (well this hit some turbulence, see Remove hwloc framework. #3029, we're probably delaying this to the future)MPI_*_get_info/set_info() (MPI_*_get_info/set_info() #2941, dependent on MPI-Forum decisions)Note that it's not normal anymore with our new time-based release strategy to have such a feature whitelist, but owing to the fact we decided to do a one-off pulled in release of v3.0.0, we need a whitelist for must-have features that won't make a branch cut sometime in early March '17.
@jsquyres
@gpaulsen
The text was updated successfully, but these errors were encountered: