Rust weighs official LTS toolchain funded by Foundation contracts

Rust developers are considering an official long-term support channel for the toolchain, potentially sold as paid contracts through the Rust Foundation. The pre-RFC, advanced by CAD97 on the internals forum, targets organizations that need defined support end dates beyond the project's regular six-week stable cadence.

CAD97 argued that the same customers who demand LTS are the ones most willing to pay, and that revenue could underwrite both extended maintenance and ongoing Rust development. An official LTS would mainly matter by existing at all: it could onboard users who later discover that staying current is painless, satisfy compliance rules that require published support policies, and let companies collaborate with the project instead of marketing unaffiliated "Vendor Rust LTS". CAD97 now favors a model with at least one year of overlapping supported releases and is preparing a survey, with other community members, to learn what timelines and prices prospective buyers expect.

Several practical objections surfaced. Most compiler work is done by volunteers following their own interests, so sustained backporting would need either dedicated Foundation funding or a reliable process for CVE-style patches. Unsoundness fixes that depend on large internal rewrites may simply be unbackportable. On the ecosystem side, an official LTS risks becoming a rallying point: distributions that already freeze toolchains could adopt it, after which users complain when libraries raise their minimum supported Rust version. Cargo's MSRV-aware resolver already steers older toolchains to compatible crate releases, and some maintainers prefer that automatic path over slowing feature adoption for everyone who tracks stable.

Josh proposed explicit project guidance that open-source maintainers owe no LTS support without a paid contract, and that any Foundation income should first cover toolchain maintenance before any surplus reaches crates that opt into extended support. Distro packagers noted that Fedora already ships every Rust release and RHEL rebases on a roughly six-month cycle, the same approach used for Clang and LLVM, leaving open the possibility of coordinated exceptions for newer system compilers.

The proposal remains pre-RFC; survey results are expected to shape the next revision.