-
Notifications
You must be signed in to change notification settings - Fork 521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
proposal: Sccache MSRV Policy #1609
Comments
I think we should provide a minimum lag and bump it on demand otherwise. I'd propose 6 months-12months to reduce friction for the compiling people in corporates, where things traditionally move at a much slower pace. |
Rust After this bump, existing blocks will be resolved, for example #1578. |
I just want to report that it is out-dated as of today. |
We have MSRV checks in CI so this should not happen. Have you used |
Sorry, you're right.
Unfortunately, I was a bit confused by the documentation about |
Hi all, I am submitting this proposal to create an MSRV policy for sccache.
TL;DR
stable - 4
as the MSRV.What's MSRV?
MSRV
meansMinimum Supported Rust Version
. By setting up MSRV, We makes sure that users who use this or newer version of rust can buildsccache
.Notice: Sccache is a binary project. The MSRV change only affects users who build sccache themselves.
Why do we need this?
Why
stable - 4
?The Rust team has been releasing a new version every 6 weeks. stable - 4 means that we are using the version that was released 6 months ago. After 6 months most of our developers or packagers should already support it. For example, Debian Rust has 1.63 in testing and 1.64 in exp.
Why extend three months?
Three months means that our maintainer only needs to update MSRV 4 times a year. It is a good balance between newer version and the work the maintainer might have.
The text was updated successfully, but these errors were encountered: