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

Next meeting: Tuesday January 2 1100 PST 2000 CET

Agenda:

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

Separation of sample queries has been merged into the JDO-831 branch.
Read-only methods are annotated.

Results are encouraging for performance.

With setup and teardown once per method:

Running tests for query.conf with datastoreidentity:
  OK Tests found: 298, started: 298, succeeded: 298, failed: 0, skipped: 0, 
aborted: 0, time: 23.993 seconds
Running tests for jdoql.conf with datastoreidentity:
  OK Tests found: 259, started: 259, succeeded: 259, failed: 0, skipped: 0, 
aborted: 0, time: 23.342 seconds
Running tests for query.conf with applicationidentity:
  OK Tests found: 298, started: 298, succeeded: 298, failed: 0, skipped: 0, 
aborted: 0, time: 24.619 seconds
Running tests for jdoql.conf with applicationidentity:
  OK Tests found: 259, started: 259, succeeded: 259, failed: 0, skipped: 0, 
aborted: 0, time: 27.754 seconds

With setup and teardown once per class:

Running tests for query.conf with datastoreidentity:
  OK Tests found: 298, started: 298, succeeded: 298, failed: 0, skipped: 0, 
aborted: 0, time: 11.687 seconds
Running tests for jdoql.conf with datastoreidentity:
  OK Tests found: 259, started: 259, succeeded: 259, failed: 0, skipped: 0, 
aborted: 0, time: 18.122 seconds
Running tests for query.conf with applicationidentity:
  OK Tests found: 298, started: 298, succeeded: 298, failed: 0, skipped: 0, 
aborted: 0, time: 15.833 seconds
Running tests for jdoql.conf with applicationidentity:
  OK Tests found: 259, started: 259, succeeded: 259, failed: 0, skipped: 0, 
aborted: 0, time: 19.417 seconds

In the branch, the git tag pre-optimize disables the strategy for optimization.

AI everyone review the code in the branch. Take a look in particular to the 
annotations and setup and teardown methods. Also look at the class inheritance.

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

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

4. Other issues

Action Items from weeks past:
[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