-
Notifications
You must be signed in to change notification settings - Fork 38
dev meeting 20220324
Present at the meeting:
- Sonja Heinze (@pitag-ha)
- Marek Kubica (@Leonidas-from-XIV)
Since the last meeting the delegate removal has been merged and the support for OPAM 1.2.2 CLI has been removed.
Sonja mentioned Guillaume's PR (#431) and the difficulties reading the name of the project from the dev-repo field. We agree that this is the way to go and if Pkg.t requires a name, we'll probably need to refactor the code a bit to be able to read it. This is a simpler way than reading it out of the Git remote and works also with Mercurial.
Sonja mentioned that Lubega created #436, but the approach is a misunderstanding between what we want to build and what the adoption team needs for the platform tool. Lubega is going to create a PR to replace calling opam lint with using the linter via the opam library which is what both adoption team and dune-release maintainers want so this is a great outcome and we're looking forward to this PR.
It has been discussed that we don't get to spend much time on dune-release because it is frequently on the bottom of the priority list. Sonja suggested a dune-release week, where all dune-release maintainers get a week to work on dune-release exclusively, thus allowing people to write code and get feedback quickly, thus potentially allowing us to move forward quickly. Marek also noted that he'll have time in August where he could tackle a number of small open issues.
We discussed Hannes issue #420. Sonja brings Marek up to speed on what the issue is, but it seems like the main problem is the unfortunate layering of happy-eyeballs < dns-client < happy-eyeballs-lwt/happy-eyeballs-mirage that makes it impossible to release them in one go. We should discuss this once all maintainers are in a meeting to figure out which direction we should take. For now there is a (somewhat unfortunate but working) workaround.
Marek explained Sonja what the reason was that we discussed making doc-generation opt-in for dune-release 2.0.0, as dune-release is not doing a great job at it and OCaml.org V3 would do a much better job at this. We agreed to ask Thibault what the timeline for OCaml.org V3 is, to release 2.0 after V3 leaves the "preview" stage.