Rust Governance, RFCs, and Editions

Why Rust is different, with Alice Ryhl

Topic 8 of 13

Published May 20, 2026 · Clip 35:55–48:49 (12:53)

The guest explains Rust's team-based governance with no benevolent dictator for life: teams sign off on everything, contentious matters are discussed at the annual Rust All Hands. She details the RFC process (motivation, guide-level and reference-level explanations, rationale/alternatives/prior art), the FCP approval flow with checkboxes and concerns, nightly feature flags, stabilization reports, and the six-week release cycle with beta testing. She covers smaller-decision mechanisms: API change proposals (ACPs) and major change proposals (MCPs), and explains editions as a way to make breaking changes without breaking people, with cross-edition interoperability.