Attendees: Tilmann Zäschke, Tobias Bouschen, Craig Russell Next meeting: Tuesday February 10 1100 PST 2000 CET
Agenda: 1. JDO doap file Recent emails: Cannot find doap file: https://raw.githubusercontent.com/apache/db-jdo-site/main/doap__JDO.rdf The file that references this has been updated. 2. JIRA JDO-856 "TCK hangs on query.conf" https://issues.apache.org/jira/browse/JDO-856 This has been reported to DataNucleus but no response yet. https://github.com/datanucleus/datanucleus-jdo-query/issues/20 Step 5 in the DataNucleus process was skipped. AI Til follow up on the process. 3. Trusted Release project https://github.com/apache/tooling-trusted-releases/pull/513 The extra trusted release project because of the misnamed doap file will be removed when they get around to it. 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 The main value of the SBOM files is for the maintainers of the project to more easily evaluate CVEs related to our dependencies. Downstream users of JDO will need to create their own SBOM for the entire set of libraries including dependencies. SBOMs have no checksums or signatures so it is not clear that publishing them has any value for downstream users. 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: [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
