Ok, I started a wiki page for this one, too: https://github.com/open-mpi/ompi/wiki/Developer-Migration-Guide:-v1.8.x-and-v1.10.x-to-v2.x
> On Apr 29, 2016, at 2:02 PM, Cabral, Matias A <matias.a.cab...@intel.com> > wrote: > > Exactly on the nail! Thanks Ralph. I've seen several comments about patches > needing to be ported from 2.x to 1.x. That will definitely be transparent to > users (apologize if I diverged the email intention), but maybe few others > will be grateful to read that wiki entry. > > Thanks! > > _MAC > > > -----Original Message----- > From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Ralph Castain > Sent: Friday, April 29, 2016 10:56 AM > To: Open MPI Developers <de...@open-mpi.org> > Subject: Re: [OMPI devel] 2.0.0 is coming: what do we need to communicate to > users? > > FWIW: I think Matias has a good point, though perhaps it belongs on a wiki > page. When we moved the BTLs down to OPAL, for example, it doesn’t impact > users, but would be worth ensuring developer’s and ISVs had a convenient > place to see what changed. > > >> On Apr 29, 2016, at 10:47 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> >> wrote: >> >> Matias -- >> >> You're probably already in pretty good shape. If you're following master >> and the v2.x branch (and you are), then your code is already in good shape. >> >> I was thinking mostly for users: transitioning from v1.8/v1.10 series to the >> v2.x series -- what kinds of user-noticeable things will they see? >> >> >>> On Apr 29, 2016, at 12:34 PM, Cabral, Matias A <matias.a.cab...@intel.com> >>> wrote: >>> >>> How about for “developers that have not been following the transition from >>> 1.x to 2.0? Particularly myself J. I started contributing to some specific >>> parts (psm2 mtl) and following changes. However, I don’t have details of >>> what is changing in 2.0. I see there could be different level of details in >>> the “developer’s transition guide book”, ranging from architectural change >>> to what pieces were moved where. >>> >>> Thanks, >>> >>> _MAC >>> >>> From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Joshua Ladd >>> Sent: Friday, April 29, 2016 7:11 AM >>> To: Open MPI Developers <de...@open-mpi.org> >>> Subject: Re: [OMPI devel] 2.0.0 is coming: what do we need to communicate >>> to users? >>> >>> Certainly we need to communicate / advertise / evangelize the improvements >>> in job launch - the largest and most substantial change between the two >>> branches - and provide some best practice guidelines for usage (use direct >>> modex for applications with sparse communication patterns and full modex >>> for dense.) I would be happy to contribute some paragraphs. >>> >>> Obviously, we also need to communicate, reiterate the need to recompile >>> codes built against the 1.10 series. >>> >>> Best, >>> >>> Josh >>> >>> >>> >>> On Thursday, April 28, 2016, Jeff Squyres (jsquyres) <jsquy...@cisco.com> >>> wrote: >>> We're getting darn close to v2.0.0. >>> >>> What "gotchas" do we need to communicate to users? I.e., what will people >>> upgrading from v1.8.x/v1.10.x be surprised by? >>> >>> The most obvious one I can think of is mpirun requiring -np when slots are >>> not specified somehow. >>> >>> What else do we need to communicate? It would be nice to avoid the >>> confusion users experienced regarding affinity functionality/options when >>> upgrading from v1.6 -> v1.8 (because we didn't communicate these changes >>> well, IMHO). >>> >>> -- >>> Jeff Squyres >>> jsquy...@cisco.com >>> For corporate legal information go to: >>> http://www.cisco.com/web/about/doing_business/legal/cri/ >>> >>> _______________________________________________ >>> devel mailing list >>> de...@open-mpi.org >>> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel >>> Link to this post: >>> http://www.open-mpi.org/community/lists/devel/2016/04/18832.php >>> _______________________________________________ >>> devel mailing list >>> de...@open-mpi.org >>> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel >>> Link to this post: >>> http://www.open-mpi.org/community/lists/devel/2016/04/18843.php >> >> >> -- >> Jeff Squyres >> jsquy...@cisco.com >> For corporate legal information go to: >> http://www.cisco.com/web/about/doing_business/legal/cri/ >> >> _______________________________________________ >> devel mailing list >> de...@open-mpi.org >> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel >> Link to this post: >> http://www.open-mpi.org/community/lists/devel/2016/04/18845.php > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/04/18847.php > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/04/18849.php -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
