Procedure on when and how to yank a release
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Would be great to have a when and how to yank a release.
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
No file, test, or entry point is named. Start by locating the website's existing release documentation and review how release procedures are organized; done means documenting when a release should be yanked and the steps for doing so.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100