rust-lang / rust-lang/libs-team
meta: Running cargo-semver-checks in reverse on std stabilisations
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 178
- Forks
- 28
- Avg merge
- 15m
- Merged PRs (30d)
- 1
Description
It has come up a couple times in the past, including very recently, that something snuck through a PR which resulted in behaviour being stabilised without us intending to do so. It's also almost-happened a few times in the past.
Since it now has support for checking stability attributes, cargo-semver-checks is being added as an experimental job to ensure that we don't break preexisting behaviour on new releases, but a point came up that running it in reverse would tell us exactly what new behaviours are getting stabilised in a given release. Is this something we'd like to approve as an experiment?
cc @obi1kenobi
Contributor guide
No contributing guide indexed for this repository
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 reading the linked issue #159856, the discussion on PR #157153, and the experimental cargo-semver-checks job described in PR #159671. Determine whether reverse checking should be approved as an experiment and document a concrete decision and scope; the issue is done when the proposal has an agreed direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100