Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell

Next meeting: Tuesday Sept 9 1100 PDT 2000 CEST

Agenda:

1. JIRA JDO-852 "Update Apache parent pom to use version 35" 
ttps://issues.apache.org/jira/browse/JDO-852

* db-jdo PR #107 https://github.com/apache/db-jdo/pull/107
* db-jdo-site PR #58 https://github.com/apache/db-jdo-site/pull/58

Ok to merge. Done.

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

No need at this time to upgrade to JDK 11 so leave it for now.

5. SBOM Support, see README.md in the root of db-jdo, section SBOM Support

Changes to create SBOM have been merged back but they are not automatically 
done. Run in api subproject results in SBOM files created in target directory.

AI Michael contact [email protected] to see if they have 
any recommendations. cc:[email protected] <mailto:[email protected]>.org

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

DB Logo planning:
AI Craig give feedback to M&P suggesting Tobias and Tilmann as contacts.
First thing to do is the db site and then the Derby and Torque can take a look.

Action Items from weeks past:

[Aug 12 2025] AI everyone investigate whether the Apache Parent POM now 
includes SBOM.
[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]

Reply via email to