We will have our regular meeting Thursday, March 8 at 9:30 AM Pacific Time 
(PST) to discuss JDO TCK issues and status. 

We use the following dial-in for audio and video. You need a Skype account to 


1. Craig is now listed as Maintenance Lead of JSR 243. Need to check the Issue 
List, public project page, and the details of the public discussion/feedback 
mechanism for JSR 243. Anything left?
2. JDO-747 "Behavior of delete() with multiple concurrent Transactions" 
3. JDO-770 "Switch from svn to git" 
4. JDO-766 "Support more JDBC-aware databases in JDO TCK" 
5. Issues with Fix Version JDO-3.2
6. JDO 3.1: Need to go through change lists in JIRA for 3.1 RC1 and 3.1 to 
prepare JCP Change Log
7. Other issues

Action Items from weeks past:
[Jan 18 2018] AI Craig talk to some git/svn Apache experts to get some advice. 
Specifically, how to preserve the svn history, how to manage the web site.
[Oct 30 2015] AI Craig: File a maintenance review with JCP
[Apr 17 2015] AI Craig: Oracle spec page on JDO need to be updated once the JCP 
Maintenance Release for JDO 3.1 is published
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL 
datastores": https://issues.apache.org/jira/browse/JDO-651?
[Feb 28 2014] AI Everyone: take a look at 
[Feb 28 2014] AI Everyone: take a look at 
[Dec 13 2013] AI Craig file a JIRA for java.sql.Blob and java.sql.Clob as 
persistent field types
[Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about 
JDOHelper methods. In process.

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 <mailto:michael.bousc...@akquinet.de>
Web:   www.akquinet.de <http://www.akquinet.de/>

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

[Facebook] <http://www.facebook.com/akquinet>  [XING]
<https://www.xing.com/companies/akquinetag>  [G+]
[LinkedIn] <https://www.linkedin.com/company/akquinet-ag>  [Twitter]

Reply via email to