On 2/13/19 3:56 AM, Dominik 'Rathann' Mierzejewski wrote:
> On Wednesday, 13 February 2019 at 06:13, Orion Poplawski wrote:
>> I'm thinking about trying to sneak in openmpi 3.1.3 before the f30
>> branch.
>> My COPR rebuilds have been looking pretty good lately so I hope it
>> will go
>> fairly smoothly. Does anyone have any objections? I'm planning on
>> starting
>> tomorrow if not.
>
> Why not 4.0.0? It was released in September 2018 and it's supposedly ABI
> compatible with 3.x:
>
https://www.mail-archive.com/announce@lists.open-mpi.org/msg00119.html
Because it's still relatively new. I've hit enough problems with
major bumps in openmpi to be a little wary. And I don't have the COPR
testing record for it. We are doing this last minute so I'm trying to
be a little more careful.
> It's a big jump from the currently packaged 2.1.6. Any idea why we are
> so behind upstream? 3.0.0 was released in September 2017, 3.1.0 in May
> 2018. 3.0.0 should have been in F27 or F28 and 3.1.0 in F29 latest.
Because no one else has stepped up to help maintain it and I'm
stretched too thin.
> Also, they say 2.1.6 is the last release in 2.1.x series, so I'd say
> an update to a supported version is a must.
I concur as well.