Hi all, I want to start by saying that this email is targeted at those writing proposals for the MPI Forum and should not be read as a plan for whether the MPI Forum will be releasing a 3.x version or a 4.x version next. I recently realized that we’ve been merging all of our proposals into the mpi-3.x branch lately, including those which explicitly say that they should not be in a 3.x release. To resolve this, I’ve reverted the commits containing MPI-4 text and moved them to a new branch called mpi-4.x. What this means for everyone else is that if you have a proposal targeted at MPI-4, you will need to make a small change to your pull request on GitHub and you’ll need to make a small change to your workflow when keeping your pull request up to date. The GitHub change is trivial (THIS WILL TAKE LESS THAN 30 SECONDS SO PLEASE DO IT RIGHT NOW!). There is a good help page from the GitHub folks here: https://help.github.com/en/articles/changing-the-base-branch-of-a-pull-reque... <https://help.github.com/en/articles/changing-the-base-branch-of-a-pull-request>. Please follow that and change your base branch from mpi-3.x to mpi-4.x. When updating the pull request (branch) in the future, instead of rebasing onto or merging with the mpi-3.x branch, you’ll use the mpi-4.x branch. Those commands look like this: For rebasing: git fetch mpi-forum # Assumes your remote that points to the “official” repository is named mpi-forum git checkout your_branch git rebase mpi-forum/mpi-4.x For merging: git fetch mpi-forum # Assumes your remote that points to the “official” repository is named mpi-forum git checkout your_branch git merge mpi-forum/mpi-4.x If you have any questions, feel free to ping me. I’m happy to help out. Thanks, Wesley