Minutes 2016 03 01

== Tuesday, March 1^st, 2016 ==

Attendees

• @diarraa
• @pygibello
• @vzurczak

What was said

• Roboconf 0.6 was released right in time.
• Tutorials were updated (in-memory, AWS) and added (Docker target).
• The meeting was focused on the defintion of the next roadmap, and in particular on how to monitor Roboconf itself to track memory leaks and so on.

• Next release will take place in April.
• No new major feature should be part of it, we will focus on tracking bugs and fixing what needs to for production usage.
• Right now, we need to find a way to monitor the DM, make a LAMP deployment run over several days and study the DM's behavior (memory, CPU, etc). This process will be iterative until the next release (next iterations will also cover agents' behavior).
• Other issues will be managed later.
• There will also be a two-week hole due to the OcciWare project (so, it will be partially related to Roboconf, but with other priorities than the next release).

• Tuesday afternoon (March, 1^st), a phone conference will take place with other Linagora teams to collect and verify their requirements about the next release.

This Week

• Make broken RabbitMQ connections repaired automatically (VZ).
• Find a way to collect system and JVM metrics about a Roboconf DM (PYG & AD).