rust-lang / rust-lang/rust-clippy
Clippy release process: Maintaining a beta branch for important uplifts
Open
Nobody has claimed this yet.
S-needs-discussion
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
Currently we don't uplift false positive fixes to beta, which means that stable can be hit with new lints that still have bugs.
Should we maintain a beta branch? If so, kinds of things qualify for uplifts? We typically have a lot of false positive fixes come in, how do we gauge whether a fix is eligible?
cc @phansch @oli-obk
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the issue's questions about maintaining a beta branch, false-positive fixes, and uplift eligibility. No files, tests, or entry points are named; done would be a documented decision and criteria for the release process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100