Skip to content
Hui Zhou edited this page Sep 15, 2026 · 9 revisions

MPICH Project Wiki

Latest release Issues ACM Software System Award

Website  ·  Downloads  ·  Documentation  ·  Mailing Lists  ·  Issues  ·  Discussions


Welcome to the MPICH GitHub wiki.

This wiki holds living, developer-facing material: usage guides for specific machines, Technical Steering Committee notes, BoF materials, and selected design documentation. For release tarballs, manpages and user guides, start at mpich.org.

Where should I go?

I want to… Go to
Install or upgrade MPICH Downloads · Guides
Run MPICH on a specific machine Usage Guides below
Ask a question or report a bug discuss@lists.mpich.org · GitHub Issues
Contribute code Contributing below
Follow project direction TSC Notes · GOVERNANCE.md

🖥️ Usage Guides

Getting MPICH running on major facilities.

🚀 MPICH Release Schedule

MPICH follows an annual release schedule. The main branch tracks development of the next release series, while an active stable branch is maintained for the current release series.

For example, in 2026, the current release series is 5.0.x, maintained in the 5.0.x branch, while the next release series, 5.1.x, is developed in the main branch. The first feature-complete beta release is typically scheduled for November. At that point, we create a new stable branch for the upcoming release series, while the main branch begins development of the following release series.

The first GA (General Availability) release is typically scheduled for January. Multiple point releases are made throughout the year as critical fixes and other important changes accumulate. Alpha releases may also be provided from the main branch when major new features are under development.

📅 Weekly MPICH Development Meeting

MPICH development meetings are open to the public and held virtually every Thursday at 9:00 a.m. US Central Time. Agendas and the meeting link are announced one day ahead on the developer mailing list — subscribe to devel@lists.mpich.org to receive them.

🗒️ TSC Notes

The Technical Steering Committee convenes twice a year; notes are published here. See GOVERNANCE.md for membership and voting rules.

📣 Events

Birds-of-a-Feather sessions — slides, notes and recordings.

Year Supercomputing Community BoF
2026 SC26 BoF —
2025 SC25 BoF —
2024 SC24 BoF CASS 2024
2023 SC23 BoF ECP 2023
2022 SC22 BoF ECP 2022
2021 SC21 BoF ECP 2021

🔧 Developer Documentation

Design notes and internal conventions for people working inside the MPICH source.

See also the contributor documentation and the legacy developer docs on the older MediaWiki site.


🤝 Contributing

GOVERNANCE.md How decisions get made: the Technical Core Team, the Technical Steering Committee, voting thresholds, current membership, and the public forums — including the weekly development meeting (Thursdays, 9am US Central, announced on devel@).
CODE_OF_CONDUCT.md Contributor Covenant 3.0. Applies to all MPICH community spaces. Report concerns to tsc@lists.mpich.org.
COPYRIGHT License terms and the copyright notice that must appear in source listings, plus the government license clause and the list of organizations that have contributed code.
Contributor Docs Contributors' License Agreement forms — individual, corporate (limited), and corporate (unlimited).

Pull requests and long-running design discussions happen on GitHub; day-to-day developer chat happens on devel@lists.mpich.org and the #mpich-dev Slack channel (access on request via devel@).

💬 Getting Help

All lists require a subscription before you can post, and all have public archives.

List Use it for
discuss@lists.mpich.org Installation and usage questions — the right place for most users
devel@lists.mpich.org Development of MPICH and its derivatives
announce@lists.mpich.org Release announcements only, roughly one message every 1–2 months

Reproducible bugs are best filed as GitHub Issues.

🔗 Elsewhere


MPICH is developed at Argonne National Laboratory with contributions from partners worldwide. See COPYRIGHT for full attribution.

Clone this wiki locally