We have nightly 1.2 tarballs too (just not listed on the web page).
To clarify our development process:
- we develop on the trunk. We typically keep that version number
higher than any existing or upcoming releases (e.g., right now, it's
"1.3" because the trunk will someday be branched for v1.3)
- when fixes are applied to the trunk, they are moved over to release
branches (e.g., the 1.1 and 1.2 release branches are the only ones
getting active work right now; the 1.0 branch is effectively dead).
This move can be done quickly, but sometimes it takes days (or longer
-- depending on the scope of the fix on the trunk).
For this specific instance, the collective changes are available on
the trunk but not yet on the 1.2 branch anyway (I'm literally in the
middle of reviewing the changes before they go over to the 1.2
branch). They should be on the 1.2 branch in the not-distant future
(a day or three?).
I'll also put up a web page showing the 1.2 nightly tarballs. Sorry;
I've had this on my to-do list for a while but just never gotten to
it (ramp-up to SC is always incredibly hectic...).
On Nov 1, 2006, at 12:51 PM, Michael Kluskens wrote:
> On Nov 1, 2006, at 10:27 AM, George Bosilca wrote:
>> PS: BTW which version of Open MPI are you using ? The one who deliver
>> the best performance or the collective communications (at least on
>> high performance networks) is the nightly release of he 1.2 branch.
> As far as I can see the only nightly releases are for the 1.3 branch.
> users mailing list
Server Virtualization Business Unit