Releasing?

[andres-erbsen]

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.

[SkySkimmer]

rocq 9.2 is not compatible with stdlib 9.0 so a release is needed anyway

[proux01]

I'll do a release once 9.2+rc1 is out. But if you want to do it feel free to (the release process is documented in dev/doc/howto_release.md and seems relatively simple), I can handle the opam and nix packaging anyway, just let me know so that we don't duplicate work.

[SkySkimmer]

I see the package for stdlib 9.1.0 in https://github.com/rocq-prover/opam but shouldn't it be in https://github.com/ocaml/opam-repository/ (where the package for 9.0.0 is)?

[proux01]

I'll let opam packagers move the opam file if they want (for instance along with adding the Rocq 9.2.0 file). Anyway, the current package is enough to build the Docker images so it's not impairing the release process for Rocq 9.2.

[andres-erbsen]

I am failing to use the new release in downstream CI. Is there still something to be done? (.opam diff)

[proux01]

Being a bit patient, Docker images have a new maintainer, let him some time to do the job, we are still very early in the release process of Rocq 9.2 so building Docker images for it is the next step there.

[proux01]

Meanwhile, I guess you can still explicitly opam install coq-stdlib.x.y.z for the version of Stdlib you want in the CI scripts (may also need an opam update).

[andres-erbsen]

This still isn't fixed: https://github.com/thery/coqprime/actions/runs/23934251655/job/69807458543?pr=94

[proux01]

The release has been done, Docker issues should be reported there.