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

Next meeting: Thursday June 15 1100 PDT 2000 CET

Agenda:

1. New JIRA JDO-828 "Set up automated mail subjects for GitHub action 
responses" https://issues.apache.org/jira/browse/JDO-828
    New PR #78 "JDO-828 - Add setup for subjects for automated GitHub emails" 
https://github.com/apache/db-jdo/pull/78
    New PR #47 "JDO-828 - Add setup for subjects for automated GitHub emails" 
https://github.com/apache/db-jdo-site/pull/47

PRs look good. Possible issue with mails from SonarCloud; can these be 
disabled? The results we are mostly looking for are displayed as comments in 
the PR anyway so a separate notice is not really needed.

2. New PR #79 "Update GitHub action versions" 
https://github.com/apache/db-jdo/pull/79
    New PR #48 "Update GitHub action versions & replace deprecated commands " 
https://github.com/apache/db-jdo-site/pull/48

Good to go.

3. JIRA JDO-827 "Consider (re-)moving JNDI support" 
https://issues.apache.org/jira/browse/JDO-827

Volunteer needed to analyze the alternatives. Originally opened for Android 
support.

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

5. JIRA JDO-822: "Verify compatibility with JDK 20" 
https://issues.apache.org/jira/browse/JDO-822

Wait until JDK 21 (LTS) to make any more changes.

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

Since this is a breaking change, we should look at releasing what we have 
before making the move. Many Java users are still on JDK 8.

7. Other issues

Java Records might be interesting to support in JDO.
https://openjdk.org/jeps/395

Action Items from weeks past:

[May 24 2023] AI Volunteers respond to JIRA JDO-827
[May 24 2023] AI Tobias add JDK 20 to the build request for GitHub for testing.
[May 03 2023] AI All: make a JIRA or two: migrate to JUnit 5; upgrade tests for 
multithreaded, first for upgrading JUnit; next for the API and next for the TCK.
[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