Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell Next meeting: November 24 1100 PST 2000 CET
Agenda: 1. PR 142 "Document builder factory revisited" https://github.com/apache/db-jdo/pull/142 Defer until 3.2.2 is shipped. Keep on the agenda. 2. Possibility of running the JDO project through Glasswing security scan - PR 136 "JNDI schema guard" https://github.com/apache/db-jdo/pull/136 Still need to remove the property PROPERTY_ALLOW_URL_SCHEME_JNDI_LOCATIONS Volunteer needed. AI Til. - PR 140 "getEnhancer() contect problem" https://github.com/apache/db-jdo/pull/140 Good to merge. AI Craig - PR 141 "classpath oracle" https://github.com/apache/db-jdo/pull/141 Still needs a bit of cleanup. Volunteer needed. AI Michael. 3. Trusted Release project Announcement Oct 21 Apache Trusted Releases (ATR) platform is Ready! see mail from Dave Fisher The trial release will be canceled by ATR team. It was just a test so no problem. We will use ATR for the 3.2.2 release coming up. 4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" https://issues.apache.org/jira/browse/JDO-812 Keep at JDK 8 for 3.2.2 and then discuss migrating to JDK 11 or JDK 17 for 3.3. 5. JDO-847 "Create SBOM files" https://issues.apache.org/jira/browse/JDO-847 Waiting on word from ATR on what is needed. AI Craig ask ATR what they need. 6. sonarcloud issues - JIRA JDO-819 "Code quality analysis" https://issues.apache.org/jira/browse/JDO-819 - JIRA JDO-823 "Fix sonarcloud issues of type Code Smells" https://issues.apache.org/jira/browse/JDO-823 - Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo - Cognitive Complexity of methods should not be too high: https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3776&severities=CRITICAL&types=CODE_SMELL&id=db-jdo - Raw types should not be used: https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3740&severities=MAJOR&id=db-jdo 7. Other issues Preparation for 3.2.2: revert main branch release number from 3.3 to 3.2.2. AI Michael use set version plugin to make the change. We need to review proposed changes from SonarCloud before 3.2.2 release. Action Items from weeks past: [Oct 06 2026] AI everyone final review of PR #142 [Sep 15 2026] AI everyone take a look at the proposed solutions PR136 - PR 141 [Jun 02 2026] AI Craig give feedback to ATR team to use jdo-dev for voting. [Jun 02 2026] AI everyone review the email and validate the release and vote using the tool. [Jun 02 2026] AI Craig ask Jarek how to respond to Q17 and use of (maintainer) in answers? [Mar 17 2026] AI Everyone look at the Sonarcloud items. [Aug 05 2025] AI everyone write to trusted release with errors in https://release-test.apache.org/projects/db-jdo + AI everyone take a look and tell the trusted release team what you find. [Jul 01 2025] AI everyone take a look at the process for alpha testing. May require a file in the dist directory to get started. [Nov 12 2024] AI Michael see if it makes sense to add Map.contains(Entry e) to the JDO API. This would be useful to have queries where e.g. the user is interested in finding all Employees where the phone number is of key "home" and value "+16508617767". [Nov 05 2024] AI Michael create a JIRA for containsEntry, include the current test case and we can continue from here. [Jul 13 2023] AI All Open a new JIRA for Android since having JNDI in the API disallows use with Android [Jun 08 2023] AI All make a JIRA: JDO support for Java Records https://openjdk.org/jeps/395 [Dec 09 2021] AI Craig: Try to contact all current/former participants in JDO development and see if and how they want to be recognized on the JDO and DB web sites.https://db.apache.org/whoweare.html [Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group members asking if they wish to continue. [Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts [Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL datastores "https://issues.apache.org/jira/browse/JDO-651
