Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] v1.8.1 release
From: Jeff Squyres (jsquyres) (jsquyres_at_[hidden])
Date: 2014-04-22 09:47:50

I spoke with Ralph last night (he's still on vacation); there has been a change of plan.

Unfortunately, the HEAD of the v1.8 branch is currently too unstable for immediate release (and we really need to do an immediate v1.8.1 release). MTT is showing a bunch of MPI-layer failures. It does not seem like a good idea to try to hurry the v1.8 branch to be releasable in the immediate timeframe (i.e., 24-48 hours).

As such, the new plan is this:

1. Release v1.8.1 which is exactly the v1.8[.0] tarball plus the session directory fixes. It will be advertised as *only* the one critical bug fix beyond the v1.8 release.

2. What we have been thinking of as "v1.8.1" will become "v1.8.2" and will be released at the same time that we had already planned (i.e., within a few weeks). This release will be mentioned in the v1.8.1 release announcement (i.e., that the "normal round of bug fixes will be coming within a few weeks", or something like that).

This will give us time to stabilize all the fixes that have been put in the v1.8 branch and have a good v1.8.2 release.

In terms of SVN, see the attached diagram for what it will look like.

On Apr 18, 2014, at 12:57 PM, Ralph Castain <rhc_at_[hidden]> wrote:

> Hello all
> As several of you know, we have had a report of a rather nasty bug in the 1.8.0 release - only manifests itself if you run as root, but some people unfortunately do so. This necessitates that we release 1.8.1 with that bug fix in the next week.
> I would like to get as many of the pending bug fixes as possible AND appropriate into that release. I'm specifically looking at bug fixes that (a) involve minimal change, and (b) affect primary use cases. Things that are at all questionable as to whether they are appropriate for the 1.8 series, involve significant code change, are in ancillary code areas, or simply aren't able to be reviewed in time will be deferred to 1.8.2.
> In this way, I am hoping to avoid releasing 1.8.1 only to be followed a few weeks later with another bug fix release. Thus, my intention is to get 1.8.1 out next week, and delay release of 1.8.2 by at least two months.
> What this means:
> * PLEASE get your CMRs reviewed ASAP. This falls primarily on Nathan and Manju, and a bit on Pasha. See my comments below as to your deadlines!!
> * I have asked Jeff to defer the OSHMEM CMRs to 1.8.2 as (a) we have to define a policy for how we deal with that code area (not every commit should be CMRd to 1.8!), and it isn't in the primary use area at this time
> * I have similarly asked Jeff to defer the Java CMR (and any new ones in that area) for the same reasons
> Note that I am on vacation all of next week, and I will *not* be responding to email during that time. I have asked Jeff to fill-in for me, and he has agreed to do so. He has my phone number in case he absolutely needs to call me about something, though I trust him enough to know that he won't do so unless absolutely necessary.
> Jeff and I have talked and agreed on a target release date for 1.8.1 of Thurs, April 24th. This means we need to roll a release candidate Tues, April 22nd. So any CMR that has *not* been cleared by COB Mon April 23rd will automatically be deferred to 1.8.2 - exceptions will *only* be accepted in cases of demonstrated catastrophic behavior.
> I appreciate everyone's cooperation, and deeply appreciate Jeff taking on the additional burden during my absence.
> Ralph
> _______________________________________________
> devel mailing list
> devel_at_[hidden]
> Subscription:
> Link to this post:

Jeff Squyres
For corporate legal information go to: