The goal is to branch annually on June 1. We're already past that -- we let it slip because we were in Chicago last week at the MPI Forum. I.e., that seemed like a good reason to let it slip.
Howard and I talked about this on the phone today (i.e., whether we should wait until the f2f meeting), and concluded, "No, let's give everyone a week and then branch." I.e., discuss tomorrow, and then branch in a week. Do you have a good reason to let it slip further? > On Jun 8, 2015, at 2:39 PM, George Bosilca <bosi...@icl.utk.edu> wrote: > > Can we wait until the f2f meeting in 2 weeks ? > > George. > > > On Mon, Jun 8, 2015 at 1:50 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> > wrote: > Developers -- > > Per our new release scheme, it's (slightly past) time to branch for v2.0.0. > > Howard and I would like to talk about branching tomorrow (9 June 2015) on the > weekly webex: > > - what features are incomplete? > - what bug fixes are coming in immanently? > - what else is needed before v2.0.0? > - how much time will these things take? > - generally: what still needs to be done for v2.0.0? > > And then -- assuming all goes well -- actually branch next Tuesday (16 June > 2015) after the weekly webex. > > -- > 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: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2015/06/17479.php > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2015/06/17480.php -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
