Re: [Mpi-forum] Non-Voting Meeting Next Wednesday - Nov 6
Hi all, Unfortunately, I wasn't able to record the meeting this week, so I wanted to send out the slides that I presented with plans for MPI 4.2: https://urldefense.us/v3/__https://docs.google.com/presentation/d/1Mo0_p4--q...  MPI 4.2 Procedures and Logistics docs.google.com https://urldefense.us/v3/__https://docs.google.com/presentation/d/1Mo0_p4--q... Please note that there's a bunch of hypothetical dates in this deck describe the timelines for MPI 4.2. We haven't confirmed (or in some cases even discussed) those dates so don't buy plane tickets or anything yet. We'll discuss more concrete dates at the December meeting. One additional thing here. If we do stick to the timeline we've tentatively agreed on (meetings in Dec, Jan, Mar, Jun), this project board shows the set of issues that would not make it into MPI 4.2. https://urldefense.us/v3/__https://github.com/orgs/mpi-forum/projects/6/view... https://urldefense.us/v3/__https://github.com/orgs/mpi-forum/projects/6/view...  MPI 4.2 • mpi-forum github.com Note that anything in the "Had Reading" column can still go in if it gets a first vote at the upcoming meeting. Lastly, we'll also need to reschedule Marc-Andre's discussion on Issue 854 for a future week. Thanks, Wes
On Oct 31, 2024, at 2:29 PM, Wes Bland <[email protected]> wrote:
Hi all,
I just wanted to remind everyone that we'll have our first non-voting virtual meeting in a long time next Wednesday at 10am US Central <https://urldefense.us/v3/__https://time.is/1000AM_6_November_2024_in_CT__;!!... >. Please plan to join us to discuss issue 852 <https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-issues/issues/85... > (Use of 'starting' for processes needs disabiguation) from Marc-Andre and I'll talk about MPI 4.2 plans along with Martin.
As usual, you can get the link for the meeting on our GitHub wiki page: https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-standard/wiki/Vi... . If you get a 404 error, make sure you're signed in first.
Thanks, Wes
participants (1)
-
Wes Bland