# pre-RFC: LTS for the Rust Toolchain

**URL:** <https://internals.rust-lang.org/t/pre-rfc-lts-for-the-rust-toolchain/24476>\
**Category:** policy\
**Created:** [July 16, 2026, 10:07pm UTC](https://internals.rust-lang.org/t/pre-rfc-lts-for-the-rust-toolchain/24476 "2026-07-16T22:07:12Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![epage](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/epage/32/3171_2.png) [@epage](https://internals.rust-lang.org/u/epage)\
**Post date:** [July 17, 2026, 1:37pm UTC](https://internals.rust-lang.org/t/pre-rfc-lts-for-the-rust-toolchain/24476/4 "2026-07-17T13:37:52Z")

</div>

Linking out to [What if we did LTSs?](https://internals.rust-lang.org/t/what-if-we-did-ltss/20375) as it covers a lot of different angles to consider.

Some thoughts in particular I want to highlight that tie into this specific proposal

- With people "stagnating" on 2-7 year old versions of Rust, doing discrete upgrades, how do we ensure there is a feedback loop if these people are broken by a new release?
- Looking over our lists of prior art, this proposal is us going from nothing to one of the longest support cycles, only seen elsewhere by commercial entities. This seems a bit aggressive for us starting out
- We would need to consider ecosystem preparation that can help with this (2-month release cycles so we have predictable calendar dates, easing long term support with `cfg_rust_version`, etc)

---

_[View the full topic](https://internals.rust-lang.org/t/pre-rfc-lts-for-the-rust-toolchain/24476)._