rust-lang / rust-lang/backtrace-rs
Tagging a new release
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 628
- Forks
- 291
- PR merge metrics
- No merged PRs in 30d
Description
Do you have any plans on tagging a new release anytime soon? Looks like master has a bunch of features which are not in the release version.
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 reviewing the differences between the master branch and the current release version. Determine which unreleased features should be included and confirm the project's release process before proceeding. Done would mean a maintainer-approved new release is tagged; the issue does not name files, tests, or a release entry point.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100