Please add x-maintenance-intent to your opam packages

[hannesm]

would you be so kind and specify your maintenance intention of your published opam packages? This would allow us to push some of these into the opam-repository archive, saving bandwidth and computation time for every opam user. I suspect that "(latest)" would be a good match for your packages (or "(none)" if you don't maintain these anymore). See https://discuss.ocaml.org/t/opam-repository-archive-clarification-of-the-opam-fields for further information.

Thanks a lot. In case you have any questions, don't hesitate to ask.

[phated]

This package follows SemVer.

[hannesm]

Thanks for that information, @phated. My question was a bit different. The opam-repository (where releases of packages are put into) was only ever growing. This is how we settled for an archiving policy (see https://github.com/ocaml/opam-repository/blob/master/governance/policies/archiving.md).

This requires package submitters to opt-in into that process, and they can do by specifying what their maintenance intention is for packages they submit.

So, even if your "follow SemVer", we'd need to know which versions of your packages should be kept (we won't archive any package that has reverse dependencies which would then be uninstallable).