nick8325 / nick8325/quickcheck
Use version milestones to label issues and PRs?
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 790
- Forks
- 130
- Avg merge
- 16h 41m
- Merged PRs (30d)
- 2
Description
I made good experience with labelling issues and PRs by version milestones (e.g. 2.18.0.0) in larger code bases (e.g. Agda).
This makes it easy to see which issue was fixed in which release.
It also helps to organize issues and PRs towards a planned release, documenting decisions (for oneself and others) what to include in the release.
Since QuickCheck is a very widely-used library, I think it would be helpful to the users to have this extra transparency.
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
The issue names no files, tests, or entry points. Review how this repository currently organizes GitHub issues and pull requests, then determine how version milestones could document release decisions and group work by release; done means an agreed, usable milestone process is defined.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100