JDO TCK Conference Call Wednesday August 17 noon PDT 21 CEST

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

Hi,

We will have our regular meeting Wednesday August 17 noon Pacific 
Daylight Time (PDT) 21:00 Central European Summer Time (CEST) to discuss 
JDO TCK issues and status.

We use the following dial-in for audio and video. You need a Skype 
account to join.
https://join.skype.com/lKWOxZDu2O5U

Agenda:

1. JIRA JDO-817 "Check Compiler warnings" 
https://issues.apache.org/jira/browse/JDO-817
see PR 54 "Update pom.xml to show compiler warnings" 
https://github.com/apache/db-jdo/pull/54 and recent checkins into branch 
tck-compiler-warnings
Changes in interfaces Query and Extent to prevent issues with 
try-with-resources.

2. JIRA JDO-818 "Use Google Java Style as the code format conventions 
for the JDO project" https://issues.apache.org/jira/browse/JDO-818
see https://google.github.io/styleguide/javaguide.html

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:

[Jun 15 2022] AI Craig verify that changing the headers now passes the 
RAT test without any other changes.
[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

Regards Michael

Minutes: JDO TCK Conference Call Wednesday August 17 noon PDT 21 CEST

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

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

Next meeting: Thursday August 25 1100 PDT 2000 CEDT

Agenda:

1. JIRA JDO-817 "Check Compiler warnings" https://issues.apache.org/jira/browse/JDO-817
see PR 54 "Update pom.xml to show compiler warnings" https://github.com/apache/db-jdo/pull/54 and recent checkins into branch tck-compiler-warnings
Changes in interfaces Query and Extent to prevent issues with try-with-resources.

Not sure if we will ever resolve all of the warnings. Removing the close() throws clause solves many of the issues. Is this an incompatible (breaking) change?

Consensus appears to be: removing the throws clause is the best thing to do.
Other opinions?

Warnings still show up with running the profile with warnings. 
mvn -Pwarnings,jodri

2. JIRA JDO-818 "Use Google Java Style as the code format conventions for the JDO project" https://issues.apache.org/jira/browse/JDO-818
see https://google.github.io/styleguide/javaguide.html

Looks good so far. Any other opinions?
Volunteer needed to create a branch and try to write a PR which addresses the style guide.

We should wait until the branch for JDO-817 is merged.

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:

[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