[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

branch master updated: Add 2022-06-07 maintainers meeting notes.

From: Mathieu Othacehe
Subject: branch master updated: Add 2022-06-07 maintainers meeting notes.
Date: Wed, 08 Jun 2022 03:35:36 -0400

This is an automated email from the git hooks/post-receive script.

mothacehe pushed a commit to branch master
in repository maintenance.

The following commit(s) were added to refs/heads/master by this push:
     new db04f0a  Add 2022-06-07 maintainers meeting notes.
db04f0a is described below

commit db04f0a4796c78596293faf642e85a1e9d9d14e0
Author: Mathieu Othacehe <>
AuthorDate: Wed Jun 8 09:33:24 2022 +0200

    Add 2022-06-07 maintainers meeting notes.
    * doc/maintainers/meetings/ New file.
 doc/maintainers/meetings/ | 44 +++++++++++++++++++++++++++++++++
 1 file changed, 44 insertions(+)

diff --git a/doc/maintainers/meetings/ 
new file mode 100644
index 0000000..8b7c568
--- /dev/null
+++ b/doc/maintainers/meetings/
@@ -0,0 +1,44 @@
+* Maintainers meeting
+** Schedule
+The 7st of June from 14:00 CET to 15:00 CET on Jami & Jitsi.
+** Agenda
+No fixed agenda -- discuss an action to take.
+** Notes
+Meeting was held on Jami & Jitsi. Efraim, Mathieu and Maxim were present.
+- The infrastructure status was discussed. We are waiting for Ricardo / MDC
+  to provide a second public IP so that we can connect to Berlin's remote
+  console even when the machine itself is down.
+  After that, the plan is to move everything to the 100TB SAN on a classic
+  ext4 partition, and possibly resume btfs boot experiments on the .129
+  machine.
+*Action* Move Berlin root to the SAN.
+  We would also like to setup the .129 machine as a staging machine. It would
+  be configured with the same configuration as Berlin, possibly using the 6
+  SSDs raid array as storage. Changes to Berlin configuration could be tested
+  out on that machine before being propagated to Berlin.
+- Cuirass experimented some troubles in May, because of a now mitigated
+  inferior issue. There are still some problems though: the "guix"
+  specification is failing and the aarch64 builds are all pending.
+*Action* Find out what's going on with the aarch64 builds.
+- The Ricardo "teams" proposition seems like a great idea. Creating a
+  get-tutors.scm script can help to find out the suitable team for patch
+  review, without having to search on the website. Creating a ML per team will
+  probably be too cumbersome.
+- The staging system tests are in good shape so we can start discussing the
+  merge of this branch as well as a new release. Maxim pointed out that for
+  the 1.3 release, the CI problems were a real limitation. The target date in
+  July is probably too optimistic. The new installer dump mechanism was
+  presented by Mathieu. This mechanism will have to be well validated before
+  releasing the 1.4 installer image.
+*Action* Check if the installer dump mechanism is working.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]