Hello everyone, Apologies for the delay, you'll find below the minutes from our last monthly meeting.
Note that you can find more details about the proposed schedule in this email sent by Serge: https://lists.apache.org/thread/7433tjfkbjgpbhkx4ox73v6rk69qjdcq Thanks, Francois --- Participants: - Thomas S. (Enonic) - Serge H. (Inoyu) - Jérome B. (Jahia) - Jonathan S. (Jahia) - Francois G. (Jahia) - Romain G. (Jahia) Meeting Minutes – Release Planning & Roadmap Discussion ## Release Planning Version 2.7.0 Proposal: Serge proposed releasing version 2.7.0 to address a critical Groovy actions performance issue, specifically targeting recompilation problems under heavy load. Elasticsearch 7 End-of-Life: Elasticsearch 7 will reach end of support on 15-Jan-2026 (Elastic EOL info). After this date, new Elasticsearch 7 environments cannot be started on Elastic Cloud. Upgrade Roadmap: Work is ongoing to upgrade to Karaf 4.4.8 and Elasticsearch 7. The target for code completion is mid-September 2025. The team proposes releasing these changes as version 3.0.0. Note: JDK 8 and 11 support will be dropped in 3.0.0; JDK 17 will be required due to Elasticsearch 9 client limitations. ## Multi-Tenancy & New Features Feature Development: Major features — including multi-tenancy support — are implemented and available on the unomi-3-dev branch. API Compatibility: A compatibility mode for jCustomer 2x APIs has been implemented, allowing existing Unomi clients to connect to multi-tenancy-enabled versions without requiring code changes. GraphQL: All GraphQL functionality is confirmed to be working, with all integration tests passing in the new development branch. Migration Considerations: Migration to the new data model will require a complete reindexation. This does not necessarily require a major version bump, as similar upgrades have occurred between previous 2.x releases. ## Karaf 4.4.8 Migration Progress Development Approach: Jerome is rebuilding Unomi project-by-project, implementing Karaf BOM for improved dependency management and addressing consistency issues. Testing Challenges: Integration test failures are being addressed, particularly those related to migration tests, which are taking longer than anticipated. OSGI Framework Updates: Significant updates to OSGI annotations (from version 6 to 8) necessitate dependency updates and package restructuring. Next Steps: The team will investigate OpenSearch integration—specifically, implementing the Elasticsearch 9 client as an additional persistence layer, rather than a full migration. ## OpenSearch Integration Considerations Early Integration Discussion: There is ongoing discussion about potentially including OpenSearch support in the 3.0.0 release, pending Jerome’s findings. No final decision has been made. Elasticsearch 9 Join Support: Identified new cross-index join capabilities in Elasticsearch 9 for possible future improvements to GraphQL implementations. Testing Recommendations: It is recommended to use Docker containers for Elasticsearch 9 integration tests, similar to the approach with OpenSearch, to facilitate debugging. ---
