Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday July 6 11:00 PDT 20:00 CET Agenda: 1. JDO-829: "api: Migrate JUnit tests to version 5" https://issues.apache.org/jira/browse/JDO-829 New PR #80 https://github.com/apache/db-jdo/pull/80 Good to go. 2. JDO-830: "tck: Migrate JUnit tests to version 5" https://issues.apache.org/jira/browse/JDO-830 Not ready for review. 3. JIRA JDO-831: "tck: improve tck tests for performance" https://issues.apache.org/jira/browse/JDO-831 To be considered after 829 and 830 are merged. 4. JIRA JDO-827 "Consider (re-)moving JNDI support" https://issues.apache.org/jira/browse/JDO-827 Tilmann has implemented a simple Mock JNDI class that allows the TCK to run, including the JNDI dependent tests. https://github.com/apache/db-jdo/pull/81 This will be the default used when running the TCK. If users prefer to use a fuller implementation (e.g. providerutil), they will need to update one configuration file that names the JNDI implementation. 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 repository.apache.org under apache.org domain to release software seems to be automatically synchronized with nexus repo Any items for the July board report? Status of JDO is ongoing, low activity. No new releases since the last report. The JDO project is continuing to work on improving support for current and future JDKs. Currently supporting JDK 7, 11, and 17. Looking to JDK 21 for the next supported release. We are also upgrading the JUnit dependency from JUnit 3 to JUnit 5 so we can more easily take advantage of potential performance improvements. Action Items from weeks past: [Jun 08 2023] AI All make a JIRA: JDO support for Java Records https://openjdk.org/jeps/395 [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. [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
