Please consider having a release / changes log again
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 814
- Forks
- 209
- PR merge metrics
- No merged PRs in 30d
Description
Context: It's been quite challenging to use a mixture of git blame and ChatGPT to hunt down a breaking change between 2.0.4 and 2.1.0 (context: https://github.com/olucurious/PyFCM/issues/380)
Ask: Please can you consider using the releases or CHANGES.rst to help others in future when versions are adjusted?
Thanks for a great project.
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 CHANGES.rst and the project's existing GitHub release history. Determine how version changes are currently recorded; done means the release or changelog process clearly documents changes between versions for future users.
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