JDO TCK Conference Call Thursday July 13 1100 PDT 2000 CEST

[Michael Bouschen <mb...@apache.org>]

Hi,

We will have our regular meeting Thursday July 13 11:00 Pacific Daylight 
Time (PDT) 20:00 Central European Summer Time (CET) to discuss JDO TCK 
issues and status.

We use the following dial-in for audio and video:
https://us02web.zoom.us/j/87074698575?pwd=bmZXeVV3dVowRHFDWk9KWFdVWjc3dz09

Agenda:

1. Number of messages send to the dev list for changes in PRs

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

3. JIRA JDO-832 "Remove RunTCK option jdo.tck.skipJndi" 
https://issues.apache.org/jira/browse/JDO-832
   PR #82 https://github.com/apache/db-jdo/pull/82

4. PR #83 "Clean up Enhancer.execute() " 
https://github.com/apache/db-jdo/pull/83

5. JDO-830: "tck: Migrate JUnit tests to version 5" 
https://issues.apache.org/jira/browse/JDO-830

6. JIRA JDO-831: "tck: improve tck tests for performance" 
https://issues.apache.org/jira/browse/JDO-831

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. JIRA JDO-822: "Verify compatibility with JDK 20" 
https://issues.apache.org/jira/browse/JDO-822
New comments

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

10. Other issues

Action Items from weeks past:

[Jun 08 2023] AI All make a JIRA: JDO support for Java Records 
https://openjdk.org/jeps/395
[May 24 2023] AI Tobias add JDK 20 to the build request for GitHub for 
testing.
[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

Minutes: JDO TCK Conference Call Thursday July 13 1100 PDT 2000 CEST

[Craig Russell <ap...@gmail.com>]

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

Next meeting: July 20 11:00 PDT 20:00 CET

Agenda:

1. Any way to reduce the number of messages sent to the dev list for changes in PRs?

AI Craig ask cdutz to look at our mail lists

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

Done and done. AI Til resolve the ticket as fixed.

Having JNDI in the API disallows use with Android. 
Volunteer needed to open a new JIRA for Android.

3. JIRA JDO-832 "Remove RunTCK option jdo.tck.skipJndi" https://issues.apache.org/jira/browse/JDO-832
  PR #82 https://github.com/apache/db-jdo/pull/82

Looks good. Resolve as fixed.

4. PR #83 "Clean up Enhancer.execute() " https://github.com/apache/db-jdo/pull/83

Work in progress based on SonarCloud issue
Refactoring does make the code more readable.
Still more work to close the class loader once it is not needed for enhancement.

5. JDO-830: "tck: Migrate JUnit tests to version 5" https://issues.apache.org/jira/browse/JDO-830
Volunteer?

6. JIRA JDO-831: "tck: improve tck tests for performance" https://issues.apache.org/jira/browse/JDO-831
Depends on JDO-830

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. JIRA JDO-822: "Verify compatibility with JDK 20" https://issues.apache.org/jira/browse/JDO-822
New comments

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

10. Other issues

Action Items from weeks past:

[Jun 08 2023] AI All make a JIRA: JDO support for Java Records https://openjdk.org/jeps/395
[May 24 2023] AI Tobias add JDK 20 to the build request for GitHub for testing.
[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
clr@apache.org