I believe that it was an oversight that no "please pick" issue was open on the repository of the stdlib (due to its former status as just a sub-package of the coq package). Because stdlib is now developed as a separate repository with its own maintenance team and capability to release independently of the Rocq Prover, its maintainers should be notified of the preparation of the Rocq Platform and given an opportunity to decide which version to ship in the Platform release (similarly to any other package).
Now, I don't think that it is a big deal for this particular release, and thus I don't think it should be delayed because of this. However, the package should be moved outside the "Dependency" level, so that the version picked is prominently visible, and in the future, stdlib maintainers should receive pick issues as any other library maintainers.
I believe that it was an oversight that no "please pick" issue was open on the repository of the stdlib (due to its former status as just a sub-package of the
coqpackage). Because stdlib is now developed as a separate repository with its own maintenance team and capability to release independently of the Rocq Prover, its maintainers should be notified of the preparation of the Rocq Platform and given an opportunity to decide which version to ship in the Platform release (similarly to any other package).Now, I don't think that it is a big deal for this particular release, and thus I don't think it should be delayed because of this. However, the package should be moved outside the "Dependency" level, so that the version picked is prominently visible, and in the future, stdlib maintainers should receive pick issues as any other library maintainers.