rocq-prover / rocq-prover/stdlib
Releasing? (Docker CI images do not support latest stdlib)
Nobody has claimed this yet.
- Dominant language
- Rocq Prover
- Stars
- 42
- Forks
- 38
- Avg merge
- 14h 6m
- Merged PRs (30d)
- 3
Description
When the stdlib split was proposed, IIRC the tentative agreement was to keep release schedule in sync with Rocq until decided otherwise. Yet looks like we completely forgot to figure out and distribute the work of actually keeping it in sync? Now it seems that there is no 9.1 release or 9.2-release candidate, and opam users are still on stdlib 9.0, blocking use of new stdlib features there.
What's to do? I definitely do not wish for opam-release management duties.
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
The issue names no file or test; start by tracing the Docker CI images and opam package listing against the Rocq release schedule. Done should mean the ownership and process for keeping stdlib releases synchronized are explicit and the required current release or candidate is distributed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100