Re: JDO TCK meeting Tuesday April 23 1100 PDT 2000 CEST
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell Next meeting: Tuesday April 30 1100 PDT 2000 CEST Agenda: 1. JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running multithreaded" https://issues.apache.org/jira/browse/JDO-835 2. JIRA JDO-836 "TCK: QueryCancel Test class fails" https://issues.apache.org/jira/browse/JDO-836 Looking at the DataNucleus test case to see if there is any caching effect. There are wildly different results running Derby versus H2. Trying to upload the test case to DataNucleus. Some permission issues to resolve... 3. 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 4. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" https://issues.apache.org/jira/browse/JDO-812 5. 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
[jira] [Updated] (JDO-840) Fix changes links on JDO news site
[ https://issues.apache.org/jira/browse/JDO-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-840: - Fix Version/s: (was: JDO 3.2.2) > Fix changes links on JDO news site > -- > > Key: JDO-840 > URL: https://issues.apache.org/jira/browse/JDO-840 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > > The current JDO site lists the JDO release on the start page. For each > release there is a link to the Jira version listing all the changes for the > particular release. For the releases older than JDO 3.2 you must be logged in > into Jira to see the list of changes. For the releases JDO 3.2.1 and JDO 3.2 > this is not necessary. > * Change the link for the older release such that it is not necessary to be > logged into Jira to see the list. > * Releases older than 3.2 may not be downloaded anymore, so th etext "You > can download the release from ..." is misleading and shoudl be skipped. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (JDO-840) Fix changes links on JDO news site
[ https://issues.apache.org/jira/browse/JDO-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen closed JDO-840. > Fix changes links on JDO news site > -- > > Key: JDO-840 > URL: https://issues.apache.org/jira/browse/JDO-840 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Affects Versions: JDO 3.2.1 >Reporter: Michael Bouschen >Assignee: Michael Bouschen >Priority: Major > > The current JDO site lists the JDO release on the start page. For each > release there is a link to the Jira version listing all the changes for the > particular release. For the releases older than JDO 3.2 you must be logged in > into Jira to see the list of changes. For the releases JDO 3.2.1 and JDO 3.2 > this is not necessary. > * Change the link for the older release such that it is not necessary to be > logged into Jira to see the list. > * Releases older than 3.2 may not be downloaded anymore, so th etext "You > can download the release from ..." is misleading and shoudl be skipped. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
