-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add x-maintenance-intent to your opam files #1879
Comments
Hello @hannesm, We maintain the latest releases of Merlin for the two last releases of the compiler and 4.14. I think that would translate into this value: Does that feels right to you ? (I mean, is that the expected syntax ?) |
Thanks @voodoos, I'll get back to you later about the syntax. Thanks for explaining what your maintenance strategy is. |
I'm confused by the "-" (since in opam, only "." is a separator between major, minor, patch, subpatch, whatever you call it), but @raphael-proust volunteered to support that in the parser for maintenance intent. Your maintenance-intent looks allright, apart from the leading "v" -- you don't need that (at least according to https://ocaml.org/p/merlin/latest your released versions are not prefixed by "v"). Thanks a lot. |
Dear Madam or Sir,
due to the opam repository archival process, we are keen to have the maintainers of packages specify their intention. We noticed that merlin has a lot of releases, and are curious what your maintenance intention is.
You can read up on the policy at https://github.com/ocaml/opam-repository/blob/master/governance/policies/archiving.md and the
x-maintenance-intent
field at https://github.com/ocaml/opam-repository/blob/master/governance/policies/archiving.md#specification-of-the-x--fields-used-in-the-archiving-processThanks a lot for taking this into consideration. Please note that adding
x-maintenance-intent
in the latest release is sufficient (please feel free to PR such a field directly to the opam-repository).Also note that if there exists a package that is to be retained in opam-repository, and this depends on a specific merlin version (not part of the maintenance-intent), this merlin version is kept -- so we don't end up in uninstallable packages.
The text was updated successfully, but these errors were encountered: