Personally I prefer a longer gap(like three months) so that we don't need to force users to upgrade to the rust version. But this may not be a big problem in the rust world as rust's release is usually quite stable and backward compatible.
On Fri, Feb 21, 2025 at 11:30 AM Renjie Liu <liurenjie2...@gmail.com> wrote: > Hi: > > As discussed in this issue > <https://github.com/apache/iceberg-rust/issues/440>, we have landed > support for using unstable rust for tooling, while stable rust for > publishing libraries. Also we enforced checking of msrv(minimum supported > rust version) in our ci. However, there is one thing undetermined yet: how > frequently should we upgrade msrv? Or the question is, as rust continues to > release new versions, what's the gap between our msrv with the latest > released rust version? > > Different projects have different policies, for example sqlx > <https://github.com/launchbadge/sqlx/blob/main/FAQ.md#what-versions-of-rust-does-sqlx-support-what-is-sqlxs-msrv> > uses > a six week gap, while tokio > <https://github.com/tokio-rs/tokio/blob/master/CONTRIBUTING.md#minimum-supported-rust-version-msrv> > uses > a six month gap. > > Different policies have different pros and cons. A short gap ensures that > our library could use newer features/improvements in rust release, while it > forces users to upgrade to newer rust versions. Longer gaps have opposite > pros and cons. > > Looking forward to hearing your thoughts! >
