Gallery versioning
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 2
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 3
Description
We've now already had a couple of issues and PRs regarding updated due to pyfar version updates (#98, #100)
It's probably a good idea to start introducing versioning the gallery and tracking the respective working pyfar version numbers in the requirements file.
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
Read issues and PRs #98 and #100 to understand the prior pyfar version updates, then inspect the repository's requirements file and existing gallery versioning. Done should mean the gallery has an agreed versioning approach and the requirements file tracks the corresponding working pyfar version consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100