Attendees: Michael Bouschen, Craig Russell

Next meeting: Tuesday August 5 1100 PDT 2000 CEST

Agenda:

0. Infrastructure is still in test mode for the Trusted Release project. 
Volunteers needed to take a look for JDO.

1. Board report input
See emails from Bryan

Activity in the JDO project has been slow but steady.

JDO web site was updated based on advice from Infrastructure that simplifies 
publishing the site. The main db.apache.org <http://db.apache.org/> site still 
needs a volunteer.

Work continues on the 3.2.2 release. No critical features or bug fixes have 
been identified.

2. Change in site publishing
anything left?
The main db.apache.org <http://db.apache.org/> site still needs the same 
changes. But it's not JDO responsibility. We can point whoever does the work to 
the changes we did for the JDO site.

3. 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

4. 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

Changes to the branch are not expected to fail, but there are still cases that 
use the xml to define the test data.

5. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812

6. SBOM Support:  changes to the actual Apache Parent POM?

7. 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
 

8. Other issues

Action Items from weeks past:

[Juk 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

Reply via email to