Subject: [MEETING] Apache Unomi monthly meeting notes - November 2026

Hello,

Notes from the November monthly catch-up. These are discussion outcomes
and proposals only. Formal decisions belong on the project mailing
lists.

Context
-------

The meeting focused on preparing Unomi 4 and 3.1 releases, the related
tracker release, and associated Jira tracking for behavioural changes.

Tracker version 2
-----------------

- Tracker version 2 works with both Unomi 3 and Unomi 4.
- Callers can choose, via JavaScript parameters, which Unomi framework
  version to use.
- Automated tests were added to check the tracker against both lines.
  These tests start containers and validate behaviour in Unomi 3 and
  Unomi 4 environments.
- Open follow-up: confirm that migration from tracker v1 to v2 is
  properly documented.

Unomi version 4
---------------

- The planned Unomi 4 work discussed for this release line is
  implemented, including the remaining dependency packaging needed for
  the release.
- The last missing dependency was packaged as an OSGi bundle to work
  around recent removal of OSGi headers in upstream artefacts.
- The Unomi 4 release candidate is otherwise ready, but it depends on
  publishing the tracker first.
- Proposal: hold the Unomi 4 vote until after the tracker release is
  out.

Unomi 3.1 backports
-------------------

- Unomi 3.1 is otherwise ready for release. Some hardening changes
  that mainly affect GraphQL have not been backported.
- GraphQL is an optional layer that the current team does not use in
  its deployments.
- Proposal: ship Unomi 3.1 without those GraphQL-specific backports
  for now, because of time constraints.
- If the community needs those GraphQL backports, an additional 3.x
  release could be proposed later. That would not be done right away.

Jira tracking
-------------

- Ideal security case discussed: private tickets that could be made
  public at release time. It is a shame the ASF does not currently
  provide that workflow.
- In the meantime, proposal: create public Jira tickets that simply
  record the changes (as improvements / updates), so we can build a
  detailed and accurate changelog for the releases.

Open questions
--------------

- Confirm whether the community actively uses the GraphQL layer. That
  may affect future maintenance choices.
- If nobody needs it, a later list discussion (for example a DEP) could
  consider whether to keep or retire that layer.
- Confirm that tracker v1 to v2 migration docs are complete.

Proposed follow-ups
-------------------

- [Serge Huber] Create the missing Jira tickets for the tracker and
  Unomi changes.
- [Serge Huber] Publish tracker version 2 so the Unomi 4 release can
  proceed.
- [Serge Huber] Check that migration from tracker v1 to v2 is properly
  documented.
- [Serge Huber] Start the Unomi 4 release process after the tracker is
  published (vote on the list).
- [Jonathan Sinovassin-Naïk] Start the Unomi 3.1 release process (vote
  on the list).

Regards,
  Serge...

Reply via email to