Attendees: Michal Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Tuesday Sep 23 1100 PDT 2000 CEST Agenda: 1. New logo for DB projects / Replace old DB icon Anything left for us? Just the copyright in the footer. https://github.com/apache/db-jdo-site/pull/59 merged. 2. JIRA JDO-851 "TCK fails result Variable tests" https://issues.apache.org/jira/browse/JDO-851 PR #105 https://github.com/apache/db-jdo/pull/105 3. New JIRA JDO-848 "Remove dependency on org.springframework:spring-beans" https://issues.apache.org/jira/browse/JDO-848 See updates to PR #104 https://github.com/apache/db-jdo/pull/104 4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" https://issues.apache.org/jira/browse/JDO-812 5. SBOM Support, see README.md in the root of db-jdo, section SBOM Support New message on security-discuss mailing list Cyclonedx files are probably good to release. Need to look at the build process. 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. Trusted Release project 8. Other issues Derby is on its way to being not-maintained. JDO is currently using an older version of Derby, so there should be little impact on us. If we do decide to migrate from Derby (perhaps h2?) there is plenty of work to be done. There is not much appetite for having the JDO team take over maintenance work for Derby. AI everyone: have your opinion heard on the Derby dev list. Action Items from weeks past: [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 c...@apache.org
