Minutes: JDO TCK Conference Call Wednesday May 3 1200 PDT 2100 CEST
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell Next meeting: Thursday May 11 1100 PDT 2000 CET Agenda: 1. 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=java%3AS3776=CRITICAL=CODE_SMELL=db-jdo Prioritize methods in the API. JDOHelper.getObjectState JDOHelper.getPersistenceManagerFactory (big catch clauses) * Raw types should not be used: https://sonarcloud.io/project/issues?resolved=false=java%3AS3740=MAJOR=db-jdo 2. JIRA JDO-822: "Verify compatibility with JDK 20" https://issues.apache.org/jira/browse/JDO-822 3. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" https://issues.apache.org/jira/browse/JDO-812 Possible issue with Android support. 4. Other issues Is there a reason to try to improve the test framework? We use vintage JUnit (based on JUnit 4). Some ideas: Migrate to JUnit 5. Set up the database once for many tests; run read-only tests with the same setup. Set up the database once for many tests; run read-only tests multithreaded https://www.baeldung.com/junit-5-parallel-tests Could we adapt JDO to support newer database implementations? https://www.datanucleus.org/products/accessplatform_4_1/jdo/samples/tutorial_cassandra.html AI volunteer make a JIRA or two: migrate to JUnit 5; upgrade tests for multithreaded 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 c...@apache.org
Re: JDO TCK Conference Call Wednesday May 3 1200 PDT 2100 CEST
Hi all, I am sick and won't be joining the conference call tomorrow. Best regards, Tobias On 02/05/2023 19:02, Michael Bouschen wrote: Hi, We will have our regular meeting Wednesday May 3 12:00 Pacific Daylight Time (PDT) 21: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. 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=java%3AS3776=CRITICAL=CODE_SMELL=db-jdo * Raw types should not be used: https://sonarcloud.io/project/issues?resolved=false=java%3AS3740=MAJOR=db-jdo 2. JIRA JDO-822: "Verify compatibility with JDK 20" https://issues.apache.org/jira/browse/JDO-822 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
JDO TCK Conference Call Wednesday May 3 1200 PDT 2100 CEST
Hi, We will have our regular meeting Wednesday May 3 12:00 Pacific Daylight Time (PDT) 21: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. 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=java%3AS3776=CRITICAL=CODE_SMELL=db-jdo * Raw types should not be used: https://sonarcloud.io/project/issues?resolved=false=java%3AS3740=MAJOR=db-jdo 2. JIRA JDO-822: "Verify compatibility with JDK 20" https://issues.apache.org/jira/browse/JDO-822 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
