Skip to content
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

Choose and enforce as MSRV #135

Open
nyarly opened this issue Aug 19, 2024 · 0 comments
Open

Choose and enforce as MSRV #135

nyarly opened this issue Aug 19, 2024 · 0 comments

Comments

@nyarly
Copy link
Collaborator

nyarly commented Aug 19, 2024

Describe the bug

The lorri project ought to choose, report and enforce an MSRV policy.

This is related both to the recent 1.80/time issue, and to lorri issues (and PRs!) related to Rust features (e.g. LazyLock.) A clear policy would make it easier for contributors to evaluate the urgency of their work, and for maintainers to decide when to accept it.

lorri builds and is backported onto the current versions of Nixpkgs, which implies an MSRV that it uses to be built. CI reflects this, so "whatever nixpkgs is using" is the de facto policy.

However, lorri development is done using Rustup, so the Rust version used there is decoupled from the deployed Rust version. Developers can maintain parity with care, though.

Additional context

Tooling around determining current versions of nixpkgs and NixOS, and the Rust toolchain available in each would be helpful. Also tooling to update documentation with versions easily.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant