Hi all, I have produced the meeting notes for our monthly meeting. Please don't hesitate to reply if you have questions, expansions, or corrections.
Best regards, Serge Apache Unomi - Monthly Community Meeting Summary Date: 8 October 2026 Time: 09:00-10:00 CEST (via Zoom) Type: Community discussion (non-binding; formal decisions must occur on the mailing lists) This email summarizes the discussions held during the monthly Unomi community meeting. In accordance with ASF policy, no formal decisions were taken during the meeting. Participants included Serge Huber (4.0 release lead), Jonathan (3.0.x release lead; joined later), and Jerome. The main focus of the meeting was the status of the 4.0.0 release. 1. Progress on Unomi 4.0.0 (formerly planned as 3.1) The version formerly referred to as 3.1 has been renamed to 4.0. Work on the updated Unomi website and documentation has progressed and is ready to be published alongside the release. A first release candidate for 4.0.0 was published. Jonathan provided detailed feedback by email. All items from that feedback have been turned into JIRA tickets and assigned to the 4.0.0 version. A blocking issue was identified around background tasks that did not run correctly outside the multi-tenant setup. This looks important to address before 4.0.0. Release-scope ideas discussed: • Blocking bugs and undocumented breaking changes are candidates to address before 4.0.0. • Minor items may be candidates to defer to a 4.0.1 or 4.1.0 release. 2. Security Reported security issues that were raised have been addressed, including items identified on an ongoing basis. Proactive review tooling continues to be used to help find issues earlier and reduce follow-up reporting work. A number of related tasks remain open. ASF security processes prioritize timely patching, which can introduce latency for other work. 3. Unomi 3.0.2 There is a need to keep progressing backports for the 3.0.2 line. A suggestion was raised that Jerome (rather than Jonathan) could review some of those backports, to get a second pair of eyes on the changes. 4. Dependabot / CI A contributor reported that a GitHub Actions runner update related to Maven broke Dependabot. Corrective pull requests were submitted for both master and the 3.0.x branch, and were merged on the morning of the meeting. Proposed Next Actions Serge (4.0 release lead): • Continue working through the tickets created from Jonathan's RC feedback • Identify which items could move to 4.0.1 / 4.1.0 • Prepare a new release candidate as soon as possible • Once the release is out, publish the updated website and announce the release on the usual channels Jonathan (3.0.x release lead) / community: • File tickets for any additional compatibility concerns between Unomi 3 and Unomi 4, even if the tickets are incomplete at first Jerome: • Review backports intended for 3.0.2 Timeline No fixed release date for 4.0.0. The working goal discussed was to ship as soon as possible, depending on progress on remaining blockers, related tasks, and follow-up from Jonathan's feedback.
