Minutes: JDO TCK meeting Thursday August 31 1100 PDT 2000 CEST

2023-08-31 Thread Craig Russell 
Attendees: Tilmann Zäschke, Tobias Bouschen, Michael Bouschen, Craig Russell

Next meeting: Thursday September 7 1100 PDT 2000 CET

Agenda:

1. New DB PMC member: Tobias Bouschen

Congratulations Tobias!

2. No DOAP for JDO

This will need an update to the DOAP for DB to include JDO, Derby, and Torque.
AI Craig: update the DOAP file to include the three subprojects.

3. Signing releases using automated release infra is a possibility for us to 
use for the next release.
AI Michael file a JDO JIRA to set up the necessary.
https://issues.apache.org/jira/browse/JDO-833

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

Final release candidate for JDK 21 is available as of August 24 2023.

8. JIRA JDO-812 "Move to JDK 11 as the lowest supported version for JDO? 
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 
Recordshttps://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

[jira] [Updated] (JDO-833) Use automated release infra for JDO releases

2023-08-31 Thread Michael Bouschen (Jira) 


 [ 
https://issues.apache.org/jira/browse/JDO-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-833:
-
Description: 
Signing releases using automated release infra is a possibility for us to use 
for the next release. 

See https://infra.apache.org/release-signing.html#automated-release-signing

  was:Signing releases using automated release infra is a possibility for us to 
use for the next release. 


> Use automated release infra for JDO releases
> 
>
> Key: JDO-833
> URL: https://issues.apache.org/jira/browse/JDO-833
> Project: JDO
>  Issue Type: Task
>  Components: site and infrastructure
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2.2, JDO 3.3
>
>
> Signing releases using automated release infra is a possibility for us to use 
> for the next release. 
> See https://infra.apache.org/release-signing.html#automated-release-signing



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (JDO-833) Use automated release infra for JDO releases

2023-08-31 Thread Michael Bouschen (Jira) 
Michael Bouschen created JDO-833:


 Summary: Use automated release infra for JDO releases
 Key: JDO-833
 URL: https://issues.apache.org/jira/browse/JDO-833
 Project: JDO
  Issue Type: Task
  Components: site and infrastructure
Affects Versions: JDO 3.2.1
Reporter: Michael Bouschen


Signing releases using automated release infra is a possibility for us to use 
for the next release. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (JDO-833) Use automated release infra for JDO releases

2023-08-31 Thread Michael Bouschen (Jira) 


 [ 
https://issues.apache.org/jira/browse/JDO-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-833:
-
Fix Version/s: JDO 3.2.2
   JDO 3.3

> Use automated release infra for JDO releases
> 
>
> Key: JDO-833
> URL: https://issues.apache.org/jira/browse/JDO-833
> Project: JDO
>  Issue Type: Task
>  Components: site and infrastructure
>Affects Versions: JDO 3.2.1
>Reporter: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2.2, JDO 3.3
>
>
> Signing releases using automated release infra is a possibility for us to use 
> for the next release. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: JDO TCK meeting Thursday August 31 1100 PDT 2000 CEST

2023-08-31 Thread Michael Bouschen 

Hi,

I'm sorry, there is a family issue I have to take care and cannot join
today.

Regards Michael

Hi,

We will have our regular meeting Thursday August 31 1100 PDT 2000 CEST
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. New DB PMC member: Tobias Bouschen

2. No DOAP for JDO

3. Signing releases using automated release infra is a possibility for
us to use for the next release.
JIRA ticket?

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
Recordshttps://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




--
Michael Bouschen
akquinet tech@spree GmbH
Bülowstraße 66 • D-10783 Berlin
Tel:   +49 30 235520-33
Fax:  +49 30 217520-12

E-Mail: michael.bousc...@akquinet.de
Web: www.akquinet.de 

Geschäftsführung: Dr. Torsten Fink, Heinz Wilming
Amtsgericht Berlin HRB 86780 • USt.-Id. Nr.: DE 225 964 680

[Facebook]  [XING]
 [LinkedIn]
 [Twitter]


smime.p7s
Description: S/MIME cryptographic signature