3.12.0 release tracking

[emillon]

known blockers

• fix: allow reuse of dispatch queues between fsevents in macOS #9009
• All 3.11 changelogs merged
• Invalid Package_version.t #9176
• Regression regarding binary artifacts and bin-available #9187
• cross-compilation regression on mirage #9199
• error with List.find_exn when cross-compiling #9239
• chore: add lang dune 3.12 #9243
• fix(memo): delay implicit output collector #9215

alpha1 (2023-11-10)

• release submitted [new release] dune (15 packages) (3.12.0~alpha1) opam-repository#24776
• triage
• go/no go for next alpha

alpha2 (2023-11-16)

• release submitted [new release] dune (15 packages) (3.12.0~alpha2) opam-repository#24805
• triage
• go/no go for next alpha

alpha3 (2023-11-22)

• release submitted [new release] dune (15 packages) (3.12.0~alpha3) opam-repository#24826
• triage
• go/no go for next alpha

release

• test mirage
• compile changelog
• release submitted [new release] dune (15 packages) (3.12.0) opam-repository#24862
• triage

post-release

• ocaml.org changelog Add changelog for Dune 3.12.1 ocaml.org#1813
• discuss post
• close milestone
• update process with lang version check
• update process with main branch checks

[Alizter]

I don't know if #9071 is worth adding to the list since it was broken in 3.11.

[emillon]

No, if that's not a regression it should not block the release.

[Alizter]

@emillon It appears to be a regression we missed in the last release however.

[emillon]

Sorry, I don't want to add more reasons to delay the release. If a fix is ready, no problem with including it, though.

[Alizter]

@emillon I'm not suggesting that it is blocking, just wanted to make sure you were aware of the issue that's all.

[Alizter]

@emillon The dune lang version needs to be bumped to 3.12.

[emillon]

@emillon The dune lang version needs to be bumped to 3.12.

Why is that? If nothing changes when (lang dune 3.11) is changed into (lang dune 3.12) I don't think there's a need to add this version.

[Alizter]

How else can users limit the Dune that their project works with? There may be reasons other than stanzas to havee the Dune version increased, such as the new odoc rules.

[emillon]

In that case they have to declare that as a piece of metadata in the opam file. Adding an explicit bound on dune in (package) should work. Actually I would not advice changing a (lang dune) version for something that's not versioned against the language,

[emillon]

I reckon it's a bit unusual. I tought there was a precedent but I can't find it so probably it didn't happen. But I don't think there's a concrete issue with not bumping the lang version if the lang is the same.

[Alizter]

Yes, I was under the false impression that we had to specify each version like we do for using which is of course incorrect. If we bump to 3.13 in the future there will be no issue.

Just to make sure we are on the same page, here is why I was surprised: Imagine you are a new user and you install dune 3.12. You have read online that you need to pick a dune-project version, and this is typically recommended as your current version of dune. If they write (lang dune 3.12) and it is not supported in this version, it might cause some head scratching.

[emillon]

That's an interesting point, yes. That's why I don't think it's useful to recommend using the latest version (personally I advice starting at 3.0 and following error messages). But dune init is going to do the right thing and the error message is going to say the right thing so I think we can keep it that way for that release.

[emillon]

Actually it's not going to work. The reason is that when we release dune 3.13, it will know about lang dune 3.12 because we assume that the set of language versions does not have holes in it. So if someone happens to use (lang dune 3.12), dune (3.13 and up) will generate "dune" >= "3.12.0" which is the incorrect bound.
Put differently, the golden rule is that all versions of dune need to agree on what 3.12 is, and if we don't add it in dune 3.12, it will be "automatically" added by the next version, and our versioning system does not support this.