Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell Next meeting: Tuesday April 9 1100 PDT 2000 CEsT
Agenda: 1. ASF - Infra newsletter for March, 2024: Policy change on use of GitHub Actions for heavy users. This does not affect the JDO project. 2. New db-jdo-site PR #51 "Update downloads.adoc" https://github.com/apache/db-jdo-site/pull/51 The change will also affect the dist repo. AI Craig merge the request and remove the artifacts from dist. The artifacts will live on in the archives. 3. JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running multithreaded" https://issues.apache.org/jira/browse/JDO-835 4. JIRA JDO-836 "TCK: QueryCancel Test class fails" https://issues.apache.org/jira/browse/JDO-836 Still looking into DataNucleus test case to explain the difference in execution time. Running a DataNucleus test case (using a different datastore H2): 21:13:25,490 (main) DEBUG [DataNucleus.Query] - JDOQL Query : Executing "SELECT max (this.x) FROM mydomain.model.Point WHERE this.x >= 0 && p2.x >= 0 VARIABLES mydomain.model.Point p2" ... 21:13:25,502 (main) DEBUG [DataNucleus.Datastore] - Using PreparedStatement "prep100: SELECT MAX(A0.X) FROM POINT A0 CROSS JOIN POINT VAR_P2 WHERE A0.X >= 0 AND VAR_P2.X >= 0" for connection "org.datanucleus.store.rdbms.datasource.dbcp2.PoolingDataSource$PoolGuardConnectionWrapper@1c6ac73c" 21:13:25,502 (main) DEBUG [DataNucleus.Datastore.Native] - SELECT MAX(A0.X) FROM POINT A0 CROSS JOIN POINT VAR_P2 WHERE A0.X >= 0 AND VAR_P2.X >= 0 21:13:28,800 (main) DEBUG [DataNucleus.Datastore.Retrieve] - SQL Execution Time = 3298 ms 21:13:28,806 (main) DEBUG [DataNucleus.Query] - JDOQL Query : Execution Time = 3316 ms Still need to add a configuration option to the TCK to know what to expect from cancel(). We should also clarify the specification/javadoc regarding what the requirements are for query cancel. 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-812 "Move to JDK 11 as the lowest supported version" https://issues.apache.org/jira/browse/JDO-812 7. Other issues Action Items from weeks past: [Jan 09 2024] AI everyone: take a look into the ResultClassRequirementsMap issue. [Jan 02 2024] AI everyone: see if anyone can see a problem with the parallel execution of tests Cast.java and SupportedOptionalMethods.java [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 c...@apache.org
