Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell Next meeting: Tuesday September 8 1100 PDT 2000 CEST
Agenda: 1. Possible bug in implementation of user defined object id classes. - New PR https://github.com/apache/db-jdo/pull/134 The patch restricts use of the ObjectIdentity constructor to only key classes that are known key classes (String, date, etc.) and not "random" user-defined classes that might cause harm if instantiated with an externally supplied key string. The known key classes can be modified by the user at runtime. The threat vector needs some more work to resolve whether having access to the list of known key classes is itself a threat, and therefore if this really is an external vulnerability. - New PR https://github.com/apache/db-jdo/pull/135 This potential vulnerability is for a harmful document instantiation when processing the configuration xml files. The mitigation can be ignored by setting another system property, so again the issue is what the JDO components are protecting from if the user can bypass the mitigation. 2. Possibility of running the JDO project through Glasswing security scan 3. Trusted Release project 4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" https://issues.apache.org/jira/browse/JDO-812 5. JDO-847 "Create SBOM files" https://issues.apache.org/jira/browse/JDO-847 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 Action Items from weeks past: [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. [Jan 13 2026] AI Craig report trusted release issues to atr team. [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 Craig L Russell [email protected]
