From Mirage dev meeting. This will be edited as we converge on release criteria:

Release criteria:

• Self hosted infrastructure using the new trees running live (e.g. website and DNS) as a fitness test
• Tooling based on the recommended OCaml Platform tools (e.g. opam, dune, merlin and so on)

Items remaining:

• mirage tool PRs
• mirage-www branch to use mirage 4

opam-monorepo release (lucas talked with nathan):

• pin-depends still missing
• 4.12 PR is around
• offline mode Add a --download-only option to pull tarides/opam-monorepo#213

upstreaming duniverse forks:

• solo5 merge
• ocaml-freestanding merge
• Zarith to the duniverse
• gmp freestanding to the duniverse
• dbuenzli's library overlays
• irmin-watcher still using jbuilder
• inotify (irmin-watcher depends on that) still uses ocamlbuild
• tcpip C stubs Use the usual layout to compile freestanding C stubs mirage-tcpip#441
• base/parsexp
• re-evaluate both https://github.com/mirage/mirage-dev/tree/mirage-4/packages and https://github.com/dune-universe/opam-overlays/tree/master/packages for what can be upstreamed
• should mirage4 (the tool) use a custom branch (or a fork) of dune-universe/opam-overlays (to avoid conflicts of other users of that repository)? -> no, maintain opam-overlays
• evaluate our previous roadmap MirageOS 4.0 draft release roadmap #994
• evaluate / close Mirage 4.0, dune and cross-compilation #1195
• how mirage4 will achieve cross-compilation? (documentation -- the mirage tool will be able to achieve this)
• io-page - [new release] io-page (2.4.0) ocaml/opam-repository#18379
• upgrade mirage-skeleton & others unikernels with the new version of functoria (objects to modules)

CI system:

• deploy ci.mirage.io with the new workflow
  • promote CI to infrastructure managed on ocurrent-deployer
• document the new workflow on mirage.io
• docs generation in ocurrent to replace docs.mirage.io
  • promote docs gen to infra managed on ocurrent-deployer
• modify ocluster-deployer to roll out mirage-4-based site

Keeping mirage3 running in LTS mode:

• nitrokey is one deployment that needs to migrate systematically
• keep a mirage-www running on mirage3 (load balancer?)