Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell

Next meeting: Tuesday December 3 1100 PST 2000 CET

Agenda:

1. New JIRA JDO-846 "Check upgrade references from javax to jakarta" 
https://issues.apache.org/jira/browse/JDO-846

Perhaps JDO API can support both javax and jakarta interfaces? 

2. New JIRA JDO-847 "Create sbom files for JDO 3.2.1 release" 
https://issues.apache.org/jira/browse/JDO-847

Questions for the security team: 

Is there a tool that can be used against a read-only distribution to create the 
SBOM? Future releases can create the SBOM during build and can be distributed 
outside the release process but already released artifacts might need a 
different approach to create the SBOM.

Once built, the SBOM is put into the target directory so it is not 
automatically included in the source release. How does the security team want 
the SBOMs to be provided to it?

3. SBOM discussion
see 
https://cwiki.apache.org/confluence/display/SECURITY/SBOM+Software+Bill+of+Materials
 

Michael has modified the 3.2.1 (released) build to generate the SBOM but it 
altered the release, so it might not be valid.

4. JIRA JDO-842 "Q class specification of candidate() method" 
https://issues.apache.org/jira/browse/JDO-842

Still working on the specification to include the latest query examples in 
Chapter 14.

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

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

Action Items from weeks past:

[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