Dear Sir or Madam,

as mentioned in the other ticket, it would be great if dune itself could specify what the maintenance intention of dune (and the other opam files in your repository) is. I suspect "(latest)" would be a good choice.

A separate but related question is about "jbuilder": would marking it as "deprecated" (i.e. flags: deprecated) be a good choice - or is there still the expectation that people will use jbuilder?

Please note: if there's a package in opam-repository that is being kept, and relies on an older version of dune / jbuilder, these versions will be kept. So it is completely safe setting the maintenance intent to [ "(latest)" ] -- there won't be any uninstallable packages due to that choice.

Of course if you plan to support the latest major version as well, please set the x-maintenance-intent field accordingly. See the full specification in https://github.com/ocaml/opam-repository/blob/master/governance/policies/archiving.md#specification-of-the-x--fields-used-in-the-archiving-process

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).