Add the news for v5.0.x branch.

[awlauria]

This is bringing back the news from 66ecc05,
which was removed with the readthedocs change.

Signed-off-by: Austen Lauria awlauria@us.ibm.com

[awlauria]

bot:aws:retest

[jsquyres]

These are legit CI errors:

/home/ec2-user/workspace/open-mpi.build.platforms/Platform/amazon_linux_2/src/docs/news/news-v5.0.x.rst:39: ERROR: Unexpected indentation.
/home/ec2-user/workspace/open-mpi.build.platforms/Platform/amazon_linux_2/src/docs/news/news-v5.0.x.rst:40: WARNING: Block quote ends without a blank line; unexpected unindent.
/home/ec2-user/workspace/open-mpi.build.platforms/Platform/amazon_linux_2/src/docs/news/news-v5.0.x.rst:59: ERROR: Unexpected indentation.

[awlauria]

Will fix today.

[awlauria]

Should be good to go.

[jsquyres]

I gave up before reaching the bottom. Please edit this a bit. Here's some guidelines:

1. Don't list user's email addresses. We don't need to publish those for spammers to harvest.
2. Only list external contributors. If someone works for one of the Open MPI regular community member organizations, we don't need to list them.
3. This file is mean to be proper english. Do not use abbreviated words (e.g., "collective ops" should be "MPI collective operations"), do not use the git commit style ("section: brief description"). Write proper english sentences with good grammar, punctuation, and capitalization.
4. Only mention things that are visible to users. Don't bother mentioning internal implementation details that have changed and are either largely or entirely invisible to the user.
5. Describe changes in the context of what the user will notice. E.g., don't say that coll/uct was added, say that UCX support was added for MPI collective operations when not using the UCX PML.
6. Group similar bullets together into sub-bullets. E.g., gather all the Fortran bullets and put them under one top-level "* Fortran updates" bullet (or something like that).
   • You can/will need to significantly re-order the bullets to do this.
   • I didn't see a bullet about the all-new documentation. There should be a top-level bullet about the new docs (and the https://docs.open-mpi.org/ web site) and then group all docs-related bullets under that (there were several docs bullets about people who helped along the way).
7. Don't list one bullet down low, and then have another bullet above it that contradicts it. Read through the entire list and make sure that this list is cohesive and self-consistent.

This is a document. It is not just a collection of independent bullets.

[gpaulsen]

Before we release, we should have a disclaimer here stating that while Open MPI v5.0.0 is NOT yet MPI-4.0 compliant, we do have a number of MPI-4.0 features implemented for developers to begin to use.

I'd also recommend moving the New MPI-4.0 features down below some of our important changes from v4.1... since majority of users will have older MPI codes.

[gpaulsen]

Lets address all of these in a post rc4 update.

[gpaulsen]

We should also add a link to (https://github.com/open-mpi/ompi-tests-public/tree/master/sessions) where users can find our MPI Sessions test cases.

[jsquyres]

bot:aws:retest

We think we resolved all suggestions. We will have another pass at documentation before release.