Skip to content
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 #2352

Open
hannesm opened this issue Jan 5, 2025 · 2 comments · May be fixed by #2353
Open

Add x-maintenance-intent to your opam files #2352

hannesm opened this issue Jan 5, 2025 · 2 comments · May be fixed by #2353

Comments

@hannesm
Copy link
Member

hannesm commented Jan 5, 2025

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 irmin 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-process

Thanks 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 irmin version (not part of the maintenance-intent), this irmin version is kept -- so we don't end up in uninstallable packages.

@art-w
Copy link
Contributor

art-w commented Jan 6, 2025

Thanks for the reminder! ocaml/opam-repository#27217

@hannesm
Copy link
Member Author

hannesm commented Jan 6, 2025

Thanks a lot. Please remember to put these into the opam files in this repository so a new release will contain them.

@art-w art-w linked a pull request Jan 6, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants