Marketing Committee Meeting 20251107

Date: 2025-11-07
Time: 12:00 UTC
Venue: Mattermost - Channel: Marketing
Called by: Marketing Committee

---

You can find the detailed meeting here:
https://mattermost.idempiere.org/idempiere/pl/1sf14nrcfjf4xgd17qs3gexeyo

Summary of the day
Participation
Meeting led by: Diego
Meeting notes and follow-up actions: Diego
Attendance list: Eugene, Diego, Carlos

1. What's new since last meeting
   • CORE
     • Development Improvements
       • IDEMPIERE-6642 Performance issue with the PO getters on X_ classes - fix deprecate warnings
     • Test Improvements
       • IDEMPIERE-6647 Fix unit tests leaving residual records in the DB
       • IDEMPIERE-6718 GridTabTest leaves residual records in C_Order and C_OrderLine tables due to missing transaction context
     • Usability Improvements
       • IDEMPIERE-6656 Unclear message when reactivating a document with reconciled posting
       • IDEMPIERE-6717 Support French when searching for constraint names
     • Bug fixes
       • IDEMPIERE-6694 2 issues related to back-dated costing. Refer to details below
       • IDEMPIERE-6720 Copy Tenant fails when there is a report archived
       • IDEMPIERE-6721 Incorrect M_AttributeInstance.Value when setting integer for number attribute type
     • Security Improvements
       • IDEMPIERE-6712 Improve algorithm for password hashing and salt (DAD-103)
     • Technical Improvements
       • IDEMPIERE-6716 Upgrade DB libraries (FHCA-7459)
   • REST
     • Technical Improvements
       • Enable "Reference REST View" field for more column reference types
     • Bug fixes
       • Error when creating a creating a UU-based parent record with UU-based child records (Foreign ID 0 not found in ParentTable_UU)
       • REST View Get by Id ignore Rest_View.WhereClause
     • Development Improvements
       • IDEMPIERE-6642 Performance issue with the PO getters on X_ classes - fix deprecate warnings
2. Potential collaboration with ZK - Follow up
   • We changed the part 2 based on feedback from @carlosruiz and sent the email to Potix.
3. Release Freeze collaboration
   • We announce the release freeze and help the core team with the following activities:
     • a) Community testing day planning
     • b) Based on the results, we decide if we need a "Developers day" to address the found issues and stabilize the release version
     • c) Simultanously we ask for: Names proposals - banner images proposals
     • d) Donation message together with the release
     • e) Create a post summarizing the key aspects of the release: new features, contributors, breaking changes, deprecated code, etc ...
     • f) We could plan an event where we assist people on the update process: recommendations, instructions, common issues, etc ...
   • We plan a future meeting on how iDempiere can integrate AI into the system