Yes. Sorry I was unclear on the title there. That’s correct. > On Oct 7, 2020, at 12:34 PM, Pritchard Jr., Howard <howa...@lanl.gov> wrote: > > HI Wesley, > > By project do you mean the MPI 4.0 ratification? > > Howard > > From: mpi-forum <mpi-forum-boun...@lists.mpi-forum.org > <mailto:mpi-forum-boun...@lists.mpi-forum.org>> on behalf of mpi-forum > <mpi-forum@lists.mpi-forum.org <mailto:mpi-forum@lists.mpi-forum.org>> > Reply-To: mpi-forum <mpi-forum@lists.mpi-forum.org > <mailto:mpi-forum@lists.mpi-forum.org>> > Date: Wednesday, October 7, 2020 at 11:11 AM > To: mpi-forum <mpi-forum@lists.mpi-forum.org > <mailto:mpi-forum@lists.mpi-forum.org>> > Cc: Wesley Bland <w...@wesbland.com <mailto:w...@wesbland.com>> > Subject: [EXTERNAL] [Mpi-forum] Last Call for MPI 4.0 Issues > > Hi all, > > (Action Item for everyone in bold below) > > For those of you who couldn’t attend the last day of last week’s MPI Forum > meeting, I’d highly recommend that you want the presentation I gave about the > process we’ll be going through over the next few months to ratify MPI 4.0. > The video is available here: > > https://youtu.be/zX1XneiVTUg?t=2249 <https://youtu.be/zX1XneiVTUg?t=2249> > (starts at 37:40) > > You can also find the slides here: > > https://github.com/mpi-forum/mpi-forum.github.io/blob/master/slides/2020/09/2020-09-30-rcm-frm-procedures.pptx?raw=true > > <https://github.com/mpi-forum/mpi-forum.github.io/blob/master/slides/2020/09/2020-09-30-rcm-frm-procedures.pptx?raw=true> > > > As part of the virtual meeting next week, I plan to hold “office hours” to > answer any questions people may have about that. I’ll also be going over the > details of exactly how some of these pieces will work where I left some gaps > in the original presentation (e.g., What will the Git branches look like? How > do we make PRs? Where do the issues go?). Everyone who will be helping review > the Standard before December should plan to attend (that’s everyone who’s > attended 3 meetings this year), chapter committees in particular. > > In anticipation of that, each person should go through any issues or pull > requests that they’ve opened on GitHub and see if there are any last minute > items for MPI 4.0. I made a pass through every PR today and cleaned up quite > a few, but there may still be some that need to be added to the agenda. To do > this, go find all of the issues where you are either an author or an assignee > (you can find how to do that in the attached image) and decide whether it > should be for MPI 4.0, MPI 4.1, MPI 5.0, or closed. There are labels for the > first three and you can just close it for the last one. As usual, if you have > questions, just ask me. If you want it to be in MPI 4.0, please also add it > to the MPI 4.0 “project” so we’ll be able to track it. > > <image001.png> > > Please note that anything that is going into MPI 4.0 really needs to be > called out in the next few weeks. Bill will be generating the release > candidate at the beginning of November and everything needs to be merged > before that happens. If something gets missed this month, it will probably > have to wait for MPI 4.1. > > Thanks, > Wes
_______________________________________________ mpi-forum mailing list mpi-forum@lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpi-forum
