JDO TCK Conference Call Thursday July 27 1100 PDT 2000 CEST
Hi, We will have our regular meeting Thursday July 27 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. Any way to reduce the number of messages sent to the dev list for changes in PRs? See email discussion with cdutz 2. Signing releases using automated release infra 3. PR #83 "Clean up Enhancer.execute() " https://github.com/apache/db-jdo/pull/83 4. JDO-830: "tck: Migrate JUnit tests to version 5" https://issues.apache.org/jira/browse/JDO-830 5. JIRA JDO-831: "tck: improve tck tests for performance" https://issues.apache.org/jira/browse/JDO-831 6. 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 7. JIRA JDO-822: "Verify compatibility with JDK 20" https://issues.apache.org/jira/browse/JDO-822 New comments 8. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" https://issues.apache.org/jira/browse/JDO-812 9. Other issues Action Items from weeks past: [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 [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
Minutes: JDO TCK Conference Call Thursday July 20 1100 PDT 2000 CEST
Attendees: Next meeting: Thursday July 27 1100 PDT 2000 CET Agenda: 1. Any way to reduce the number of messages sent to the dev list for changes in PRs? See email discussion with cdutz. We may be able to thread more results. Need to look into removing the commit id from the subject. The list jdo-commits might not have much useful information so it might be useful to unsubscribe from that list. Volunteer to investigate the jdo asf.yaml further. 2. Signing releases using automated release infra For future reference, we may want to look into using a GitHub Action to prepare release artifacts. This may reduce the number of steps in our release process, but the energy required to set it up may be more than just do the process as it exists. 3. PR #83 "Clean up Enhancer.execute() " https://github.com/apache/db-jdo/pull/83 Good progress. Still an issue with creating and disposing the URLClassLoader. Not quite ready to merge. 4. JDO-830: "tck: Migrate JUnit tests to version 5" https://issues.apache.org/jira/browse/JDO-830 5. JIRA JDO-831: "tck: improve tck tests for performance" https://issues.apache.org/jira/browse/JDO-831 6. 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 7. JIRA JDO-822: "Verify compatibility with JDK 20" https://issues.apache.org/jira/browse/JDO-822 New comments 8. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" https://issues.apache.org/jira/browse/JDO-812 9. Other issues Action Items from weeks past: [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 [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
Re: [PR] Clean up Enhancer.execute() (db-jdo)
sonarcloud[bot] commented on PR #83: URL: https://github.com/apache/db-jdo/pull/83#issuecomment-167685 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=db-jdo=83) [](https://sonarcloud.io/project/issues?id=db-jdo=83=false=BUG) [](https://sonarcloud.io/project/issues?id=db-jdo=83=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=db-jdo=83=false=BUG) [](https://sonarcloud.io/project/issues?id=db-jdo=83=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=db-jdo=83=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=db-jdo=83=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=db-jdo=83=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=db-jdo=83=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=db-jdo=83=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=db-jdo=83=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=db-jdo=83=false=CODE_SMELL) [1 Code Smell](https://sonarcloud.io/project/issues?id=db-jdo=83=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=db-jdo=83) No Coverage information [](https://sonarcloud.io/component_measures?id=db-jdo=83=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=db-jdo=83=new_duplicated_lines_density=list) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jdo-dev-unsubscr...@db.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Clean up Enhancer.execute() (db-jdo)
sonarcloud[bot] commented on PR #83: URL: https://github.com/apache/db-jdo/pull/83#issuecomment-1644423598 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=db-jdo=83) [](https://sonarcloud.io/project/issues?id=db-jdo=83=false=BUG) [](https://sonarcloud.io/project/issues?id=db-jdo=83=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=db-jdo=83=false=BUG) [](https://sonarcloud.io/project/issues?id=db-jdo=83=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=db-jdo=83=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=db-jdo=83=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=db-jdo=83=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=db-jdo=83=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=db-jdo=83=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=db-jdo=83=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=db-jdo=83=false=CODE_SMELL) [2 Code Smells](https://sonarcloud.io/project/issues?id=db-jdo=83=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=db-jdo=83) No Coverage information [](https://sonarcloud.io/component_measures?id=db-jdo=83=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=db-jdo=83=new_duplicated_lines_density=list) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jdo-dev-unsubscr...@db.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
