Skip to content
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

Closed
6 tasks done
hppritcha opened this issue Mar 6, 2017 · 12 comments
Closed
6 tasks done

v3.0.0 feature whitelist #3107

hppritcha opened this issue Mar 6, 2017 · 12 comments
Assignees
Milestone

Comments

@hppritcha
Copy link
Member

hppritcha commented Mar 6, 2017

Per the 2/28/17 devel core minutes the following items made it to the v3.0.0 feature whitelist:

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

@jjhursey
Copy link
Member

jjhursey commented Mar 6, 2017

The Hook framework was merged into master as part of PR #2773 - so that can be checked off.

@gpaulsen
Copy link
Member

gpaulsen commented Mar 7, 2017

The get/set Info stuff is very close, passed review, and just needs a rebase: PR #2941.

@hppritcha
Copy link
Member Author

hppritcha commented Mar 7, 2017

We will delay #2941 and hwloc removal to a future release.

@hppritcha
Copy link
Member Author

@jladd-mlnx where are we with these UCX related features?

@hppritcha
Copy link
Member Author

UCX multi-threading PR should be posted for master by end of this week according to @jladd-mlnx

@jladd-mlnx
Copy link
Member

@hppritcha Done PR: #3168

@hppritcha
Copy link
Member Author

@rhc54 any update on when PMIX 2 will get in to this branch?
@gpaulsen please add to agenda for this weeks con-call

@rhc54
Copy link
Contributor

rhc54 commented Apr 24, 2017

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.

@hppritcha
Copy link
Member Author

Thanks for the update Ralph! Going with v1.2 sounds like the right thing to do at this point.

@rhc54
Copy link
Contributor

rhc54 commented Apr 24, 2017

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)

@gpaulsen
Copy link
Member

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.

@bwbarrett
Copy link
Member

We've pulled all the whitelist items into 3.0 and are back to bugfix only, so closing this ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants