[BD-46] Legacy changelog
Open
Nobody has claimed this yet.
- #2605 by @peterkulko — closed without merging
bug
raccoon-gang
- Dominant language
- JavaScript
- Stars
- 140
- Forks
- 100
- Avg merge
- 1h 3m
- Merged PRs (30d)
- 30
Description
We currently have a legacy changelog on the Paragon site documentation. Last change date 2022-11-10 (v 20.18.1). This functionality is in demand for developers to update to new versions of Paragon and track new changes to Paragon.
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
Begin with the legacy changelog on the Paragon site documentation linked in the issue, then review closed pull request #2605 for prior context. Confirm the desired source and update process with maintainers; done means the changelog is current and developers can use it to track Paragon releases.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100