CosmoStat / CosmoStat/sp_validation
Decide v1.6 inclusion in release (caveated)
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 5
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 19
Description
Decide whether to release v1.6 alongside v1.4.6.3, with an explicit caveat that it is not validated to the same level. Open.
Context: Paris meeting notes
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 the linked Paris meeting notes and review how releases v1.6 and v1.4.6.3 are prepared in this repository. Done means reaching and documenting a release decision, including the explicit caveat about v1.6 validation; the issue does not name files, tests, or an implementation entry point.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100