On 08/09/2012 01:41 PM, Jeff Squyres wrote:
On Aug 9, 2012, at 5:53 AM, ESCOBAR Juan wrote:

Perhaps a Boeotian question .

Why the nightly version are called 1.9.xxx ??
http://www.open-mpi.org/nightly/trunk/

are they from 1.6 (or 1.7 series) ?
Neither.  They're from the v1.9 series.  :-)  Keep in mind that we have active 
nightly tarball series right now: v1.6, v1.7, and v1.9.

Here's our numbering scheme:

- In general, an even 2nd number of OMPI's release number indicates a "super stable" 
series, and an odd number indicates a "feature release" series.  See 
http://www.open-mpi.org/software/ompi/versions/ for more details.

:-[ Thank you Jeff .
:-[ Yes , I've already read this page ...
:-[ My mistake ...
:-[ I was little lost in the web pages

The version I was looking for is in this page :
http://www.open-mpi.org/nightly/
and then link
=> *v1.6 series* <http://www.open-mpi.org/nightly/v1.6/>
=> openmpi-1.6.1rc2r26972.tar.gz 
<http://www.open-mpi.org/nightly/v1.6/openmpi-1.6.1rc2r26972.tar.gz>

... but as I'am also interested in testing the Open-MPI/CUDA feature ( with 
potentially pgi-acc or open-acc directive )
I've 'googled' and finish in the the Open-MPI  'trunck' .

=> this Open-MPI/CUDA feature will be only in the 1.9 serie or also on 1.7/1.8 ?

A+
Juan .




- v1.6.x is the current stable release series.
   - We have a specific branch in our SVN repository for the v1.6.x series.

- v1.7.x is the upcoming feature release series (we anticipate v1.7.0 in 
October or so).
   - We have a specific branch in our SVN repository for the v1.7.x series.

- Per our scheme, v1.7.x will eventually morph into v1.8.x.
   - Meaning: the v1.7.x SVN branch will eventually be renamed to be v1.8.x.

- Hence, our SVN development trunk -- where we do most of our day-to-day work -- is the 
*next* series pair beyond 1.7/1.8.  It's therefore "v1.9".

Make sense?



--
Juan ESCOBAR
Support MESONH
Laboratoire d'AƩrologie, O.M.P.
14 avenue Edouard Belin
31400 - TOULOUSE
Tel : +33 (0)5-61-33-27-49
Fax : +33 (0)5-61-33-27-90

Reply via email to