-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Meetings agenda
Marcello Seri edited this page Nov 21, 2023
·
30 revisions
- Always start the meeting asking how’s everyone doing and if they have any issues
- Does anyone want to write the meeting notes this week?
- Add any major changes (CI, new maintainers, …) to the meeting notes
For the upcoming meeting:
- add an upper bound on ocaml 5.0 (or even 4.08) or on all result < 1.5 packages: https://github.com/ocaml/opam-repository/issues/24263
Typical tasks:
- Are there been any change in the infrastructure? (opam-repo-ci, machines, Github Actions, …)
- If so make sure they are noted in ocaml/infrastructure and in the README (such as for a change in the tested platforms)
- Are there big issues to discuss first?
- Are there upcoming surprises that we should know about?
- e.g any upcoming big PRs (dune, JaneStreet packages, Tezos, …)?
- Progress on the documentation for maintainers
- Progress on the documentation for publishers
On quiet weeks:
- revisit long standing issues and PRs, close them if deemed necessary.