Rust version policy for patches

[mcroomp]

Hi there, I was talking with the maintainer of jpeg_encoder about using wide, and the issue of the rust version policy came up. The concern was that if there was a critical issue that had to be patched, which also resulted in a version increase, everyone downstream would also need to update their rust version, which would be quite disruptive.

Have you put any thought into whether the policy could only apply to major/minor and not patch?

Thanks!

[Lokathor]

Well there's a few things here.

1. with a leading 0 in the version number then cargo just ignores that position, treating the version as basically 0.major.minor.
2. bumping the middle number when the leading number is 0 is a breaking change release, by cargo's system.
3. If you mean that only breaking releases are minimum rust version bumps, that's basically not reasonable. That's exactly what the new resolver is working to fix in the long term.

So when you say "only minor version updates bump msrv", if you mean middle number bumps that are currently seen by cargo as breaking changes, that's not the long term aim here.

What people should start doing is using resolver 3 so that they get the highest version supported by their version of rust.

[Lokathor]

I'm sorry for the close/reopen, my phone's touch screen was going a little haywire.

[Lokathor]

Actually, I'm going to just close this in favor of centralizing discussion where it began, within that PR.