Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell Next meeting: Tuesday March 31 1100 PDT 2000 CEST
Agenda: Breaking news: Projects that use Trivy may be subject to credential theft. JDO is not affected. There is a project underway to make a tool available to Java ASF projects to statically analyze code and compare to known CVEs. The project intends to apply as an incubator podling. More later. 1. PR #118 Split Github Action for DataNucleus 5 and 6 https://github.com/apache/db-jdo/pull/118 The CI builds now support JDK 8, JDK 11, JDK 17, and JDK25 with sparse runs on MacOS, Windows, and Ubuntu. Good to merge. 2. Trusted Release project 3. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" https://issues.apache.org/jira/browse/JDO-812 4. JDO-847 "Create SBOM files" https://issues.apache.org/jira/browse/JDO-847 5. 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 For next meeting, add the sonar cloud link: https://sonarcloud.io/project/issues?rules=java%3AS3740&issueStatuses=OPEN&id=db-jdo Look at the Rule category It might be possible to tell SonarCloud not to report certain types of issues. We will look at the issues and decide which to focus on for the next release and try to tell SonarCloud to ignore those that we do not intend to fix. 6. Other issues Action Items from weeks past: [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]
