On Aug 29, 2016, at 11:42 PM, C Bergström <cbergst...@pathscale.com> wrote: > > Paul - Is this your typical post? I can't tell if you're trying to be > rude or it's accidental.
I believe that multiple people on this thread are reacting to the passive-aggressive tones and negative connotations in charged replies. So maybe we can all knock it off, and just move forward with some fact-based discussions. I'd like to see: 1. The specific link error that we're talking about. 2. All the information listed on https://www.open-mpi.org/community/help/ for compile/build problems. 3. More complete patches for fixing the issues. Specifically, the 3 provided patches fix certain issues in some parts of the code base, but the same issues occur in other places in the code base. As such, the provided patches are not complete. ----- For the moment, I think talking about this stuff in the context of v1.10.x is sufficient. As the v1.10.x release manager (Ralph) stated, he would like to see the case made that this is necessary, a complete solution, and will not be a burden to maintain in the future. As one of two release managers for v2.x, I'd like to hear if the customer is unsatisfied using an older version of Open MPI (potentially v1.6.x, or v1.8.x, or *possibly* v1.10.x) before we talk about the v2.x series. I think that since SUSE 10 was EOL before Open MPI v2.0.0 was released, adding in legacy support to the brand-new v2.x series has a significantly higher bar to meet. -- Jeff Squyres 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
