You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by Michael Bouschen <mb...@apache.org> on 2023/05/31 19:01:30 UTC
JDO TCK Conference Call Thursday June 1 1100 PDT 2000 CEST
Hi,
We will have our regular meeting Thursday June 1 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. New JIRA JDO-827 "Consider (re-)moving JNDI support"
https://issues.apache.org/jira/browse/JDO-827
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-822: "Verify compatibility with JDK 20"
https://issues.apache.org/jira/browse/JDO-822
4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version"
https://issues.apache.org/jira/browse/JDO-812
5. Other issues
Action Items from weeks past:
[May 24 2023] AI Tobias: write a JDO JIRA and GitHub PR to see what
happens with Mailing list configurations
[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
[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
Re: JDO TCK Conference Call Thursday June 1 1100 PDT 2000 CEST
Posted by Tobias Bouschen <to...@googlemail.com.INVALID>.
Hi all,
I can't make it to the conference call today. See you next week.
Best regards,
Tobias
On 31/05/2023 21:01, Michael Bouschen wrote:
> Hi,
>
> We will have our regular meeting Thursday June 1 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. New JIRA JDO-827 "Consider (re-)moving JNDI support"
> https://issues.apache.org/jira/browse/JDO-827
>
> 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-822: "Verify compatibility with JDK 20"
> https://issues.apache.org/jira/browse/JDO-822
>
> 4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version"
> https://issues.apache.org/jira/browse/JDO-812
>
> 5. Other issues
>
> Action Items from weeks past:
>
> [May 24 2023] AI Tobias: write a JDO JIRA and GitHub PR to see what
> happens with Mailing list configurations
> [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
> [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 June 1 1100 PDT 2000 CEST
Posted by Craig Russell <ap...@gmail.com>.
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Thursday June 8 1100 PDT 2000 CET
Agenda:
1. New JIRA JDO-827 "Consider (re-)moving JNDI support" https://issues.apache.org/jira/browse/JDO-827
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-822: "Verify compatibility with JDK 20" https://issues.apache.org/jira/browse/JDO-822
4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" https://issues.apache.org/jira/browse/JDO-812
5. Other issues
update on [May 03 2023] AI All: make a JIRA or two: migrate to JUnit 5; upgrade tests for multithreaded
Perhaps the best way to start is to first modify the API module to use JUnit 5.
Currently tests are written in the vintage JUnit 3 interface.
https://stackoverflow.com/questions/47158583/executing-junit-4-and-junit-5-tests-in-a-same-build
AI: perhaps best to split the JIRA-to-be into a few: first for upgrading JUnit; next for the API and next for the TCK.
Action Items from weeks past:
[May 24 2023] AI Tobias: write a JDO JIRA and GitHub PR to see what happens with Mailing list configurations
[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
[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