release instructions as written do not actually issue a prerelease
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 838
- Forks
- 123
- Avg merge
- 7h 58m
- Merged PRs (30d)
- 12
Description
I ran the steps in release.rst and at the point where I expected to ask for a review on a release candidate, I saw a final release on PyPI, so I just hit the red admin-merge button. If there are issues with that release we can yank it and issue another one. This should probably be fixed.
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 with release.rst and reproduce the documented release steps through the point where a release candidate review is expected. Update the instructions so that this step issues a prerelease rather than a final PyPI release, then verify the revised process reaches the intended review point.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100