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/09/06 15:49:25 UTC
JDO TCK meeting Thursday September 7 1100 PDT 2000 CEST
Hi,
We will have our regular meeting Thursday September 7 1100 PDT 2000 CEST
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. No DOAP for JDO
2. JIRA JDO-833 "Use automated release infra for JDO releases"
https://issues.apache.org/jira/browse/JDO-833
3. JDO-830: "tck: Migrate JUnit tests to version
5"https://issues.apache.org/jira/browse/JDO-830
4. JIRA JDO-831: "tck: improve tck tests for
performance"https://issues.apache.org/jira/browse/JDO-831
5. 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
6. JIRA JDO-822: "Verify compatibility with JDK
20"https://issues.apache.org/jira/browse/JDO-822
New comments
7. JIRA JDO-812 "Move to JDK 11 as the lowest supported
version"https://issues.apache.org/jira/browse/JDO-812
8. Other issues
Action Items from weeks past:
[Aug 31 2023] AI Craig: update the DOAP file to include the three
subprojects.
[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
Recordshttps://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 meeting Thursday September 7 1100 PDT 2000 CEST
Posted by Craig Russell <ap...@gmail.com>.
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday Sept 14 1100 PDT 2000 CET
Agenda:
1. No Description Of A Project for JDO
Craig is working on it. The authoritative file will go into the db-jdo-site repo.
2. JIRA JDO-833 "Use automated release infra for JDO releases" https://issues.apache.org/jira/browse/JDO-833
3. JDO-830: tck: Migrate JUnit tests to version 5 https://issues.apache.org/jira/browse/JDO-830
4. JIRA JDO-831: tck: improve tck tests for performance https://issues.apache.org/jira/browse/JDO-831
5. 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
6. JIRA JDO-822: "Verify compatibility with JDK 20"https://issues.apache.org/jira/browse/JDO-822
New comments
7. JIRA JDO-812 "Move to JDK 11 as the lowest supported version"https://issues.apache.org/jira/browse/JDO-812
8. Other issues
The EU Cyber Resilience Act is working its way through the legislative process and the way it is currently worded has significant negative implications for all open source projects, including all ASF projects.
Action Items from weeks past:
[Aug 31 2023] AI Craig: update the DOAP file to include the three subprojects.
[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 Recordshttps://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