Export MPI_VERSION to docs.

[awlauria]

No description provided.

[jsquyres]

I think you don't want to change most of the "MPI-3.1" references in the man pages, because they refer to specific sections in the MPI-3.1 document, which may (did) change in other versions of the MPI document.

[awlauria]

@jsquyres The rationale for a lot of these is once we claim v4.0 support, we would update these references to the new v4.0 sections if they change. Right now we claim v3.1 support, so it makes sense that we reference the v3.1 sections, but I can change any that don't make sense to change.

[jsquyres]

@jsquyres The rationale for a lot of these is once we claim v4.0 support, we would update these references to the new v4.0 sections if they change. Right now we claim v3.1 support, so it makes sense that we reference the v3.1 sections, but I can change any that don't make sense to change.

I hear what you're saying, but you'll somehow also need to update the section numbers for the MPI-4.0 doc, too. Otherwise, the content becomes factually incorrect.

That being said, even though it's "odd", it's technically correct to still cite the MPI-3.1 doc and a specific section in it: that's a fixed reference, and is still correct, even if Open MPI supports MPI-4.0.

[awlauria]

@jsquyres The rationale for a lot of these is once we claim v4.0 support, we would update these references to the new v4.0 sections if they change. Right now we claim v3.1 support, so it makes sense that we reference the v3.1 sections, but I can change any that don't make sense to change.

I hear what you're saying, but you'll somehow also need to update the section numbers for the MPI-4.0 doc, too. Otherwise, the content becomes factually incorrect.

That being said, even though it's "odd", it's technically correct to still cite the MPI-3.1 doc and a specific section in it: that's a fixed reference, and is still correct, even if Open MPI supports MPI-4.0.

Correct - before upping the version to v4.0 (this PR does not change the version - just makes sure it's propagated) - these references will need to be updated to the correct section. I figured that is just something we should do anyway, once we claim v4.0 support and are ready to bump the actual version. 🤷

Anyway - I can revert this commit if is more trouble than it is worth.

[jsquyres]

Anyway - I can revert this commit if is more trouble than it is worth.

Let's remove all the places where you changed "MPI-3.1 section xyz...", and leave that as a fixed, hard-coded reference. There were a few places where it was ok to update to MPI-|mpi_version|.|mpi_subversion|.

[awlauria]

Anyway - I can revert this commit if is more trouble than it is worth.

Let's remove all the places where you changed "MPI-3.1 section xyz...", and leave that as a fixed, hard-coded reference. There were a few places where it was ok to update to MPI-|mpi_version|.|mpi_subversion|.

Done

[awlauria]

@jsquyres is this good to go?

[awlauria]

@jsquyres I made that change, but you might want to refresh as it seems you might be looking at a stale version. The spawn_multiple file is not touched anymore.

[awlauria]

bot:aws:retest