-
Notifications
You must be signed in to change notification settings - Fork 107
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
MSRV policy #346
Comments
For anyone else seeing this, the MSRV in Looks like you are asking for a roughly two year MSRV policy. Could you expand on what requirements on driving that low of an MSRV and why older versions of We are looking to re-implement This wouldn't just impact Key dependencies would include
This would also prevent us from keeping our
See also rust-lang/libs-team#72 |
Just want to add that bstr 1.0 chose its MSRV for this specific feature. |
I write some security-critical software that uses toml for configuration. Being security-critical using rustup is not a secure-enough way to get the compiler. Debian packages are the way to go and there is 1.48 in Debian stable.
Actually, they are right now. If there are any bugs found in older versions then it could become a problem. Thankfully, being used for configuration only security vulnerabilities are not that huge issue. So an alternative policy "MSRV is 1.60 but we will accept PRs backporting bug fixes to older versions of the crate" would be also fine. This implies either minor version needs to be bumped with MSRV bump or some versions may get 4-component version numbers ( |
I think we could do a one-off 0.5 release that includes the needed deprecations while maintaining the old MSRV. 0.6+ would then be using the regular MSRV. |
Sounds good, thanks! |
A semver increase for this would be very appreciated for my use of |
It doesn't seem to be explicitly documented, so going off of toml-rs#346
Alright, I've setup the release process for a |
The
toml
crate originally had lower (implicit) MSRV. Would it be possible to lower it back to at least 1.48?The text was updated successfully, but these errors were encountered: