Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Tuesday April 21 1100 PDT 2000 CEST Agenda: 1. Bump org.apache.logging.log4j:log4j-core from 2.25.3 to 2.25.4 in /tck PR #122 https://github.com/apache/db-jdo/pull/122 Merged. 2. Trusted Release project Making some progress. The release artifacts need to be created from a clean workspace or errors may occur such as jdo-3.3-SNAPSHOT-source-release.tar.gz: jdo-3.3-SNAPSHOT/ext/fscontext.jar: Archive link target escapes root (/Users/clr/Downloads/fscontext-4.2.jar) 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 We will need advice from the tooling team about where and how to create the sbom files. 5. sonarcloud issues New PR #121 https://github.com/apache/db-jdo/pull/121 * 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 Several issues are "accepted" so they do not show up on the output. AI Michael remove these from accepted and possibly add them to @IgnoreWarnings Should we have a println function in the Utilities class to reduce the number of warnings? 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 -- Michael Bouschen tech@spree GmbH Bülowstraße 66 • 10783 Berlin Tel: +49 30 235520-0 E-Mail: [email protected] Web: www.spree.de <http://www.spree.de/> tech@spree GmbH, Berlin Geschäftsführung: Dr. Torsten Fink, Heinz Wilming Amtsgericht Berlin HRB 86780 • USt.-Id. Nr.: DE 225 964 680 USt.-Id. Nr.: DE 225 964 680 [LinkedIn] <https://www.linkedin.com/company/tech-at-spree-gmbh/> Craig L Russell [email protected] Craig L Russell [email protected]
