Minutes: JDO TCK Conference Call Friday, Oct 28, 9 am Pacific Time

2011-10-28 Thread Craig L Russell

NOTE: Daylight Savings ends next week for everyone outside the USA.

Attendees: Michelle Caisse, Matthew Adams, Michael Bouschen, Craig  
Russell


Agenda:

1.  JDO 3.0.1 release issues

The 3.0.1 api test now fails. Solution: merge some of the trunk fixes  
into the branch before release.


2.  Spec updates for JDOQL : Support for further methods (String,  
Enum, Date, JDOHelper) https://issues.apache.org/jira/browse/JDO-658


Looks good.

3.  Other issues

JDO-700 was fixed. Good job.

What about archiving the obsolete projects? Maybe move e.g. api11,  
api2-legacy, etc. from trunk to a new archive directory?


 Action Items from weeks past:

 [April 8 2011] AI Craig comment on https://issues.apache.org/jira/browse/JDO-617 
 re the utility of the update operator.
 [Sep 23 2011] AI Michael prepare spec update for JDOQL changes  
(JDO-658) and document restrictions on Enum.ordinal and Enum.toString.  
Create new JIRA for Math methods in JDOQL.
 [Sep 23 2011] AI Michael document when changing dependencies (to  
DataNucleus) it's necessary to rebuild the exectck project before  
running tck.


Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:craig.russ...@oracle.com
P.S. A good JDO? O, Gasp!



[jira] [Updated] (JDO-699) Archive unmaintained modules

2011-10-28 Thread Matthew T. Adams (Updated) (JIRA)

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

Matthew T. Adams updated JDO-699:
-

Description: There are many modules in the trunk of the JDO source repo 
that are no longer maintained.  I propose to create a new directory archive 
as a peer to trunk, branches, releases, and site, then svn-move them from trunk 
to archive.  (was: There are many modules in the trunk of the JDO source repo 
that are no longer maintained.  I propose to delete them from trunk.)
Summary: Archive unmaintained modules  (was: Delete unmaintained 
modules)

 Archive unmaintained modules
 

 Key: JDO-699
 URL: https://issues.apache.org/jira/browse/JDO-699
 Project: JDO
  Issue Type: Improvement
  Components: api11, api2-legacy, btree, core2, enhancer2, fostore2, 
 model2, query2, ri11, runtime2, tck11, tck2-legacy, util2
Affects Versions: JDO 3 maintenance release 1
Reporter: Matthew T. Adams
Assignee: Matthew T. Adams
 Fix For: JDO 3 maintenance release 1


 There are many modules in the trunk of the JDO source repo that are no longer 
 maintained.  I propose to create a new directory archive as a peer to 
 trunk, branches, releases, and site, then svn-move them from trunk to archive.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (JDO-699) Archive unmaintained modules

2011-10-28 Thread Matthew T. Adams (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/JDO-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13138558#comment-13138558
 ] 

Matthew T. Adams commented on JDO-699:
--

WDYT, everyone?

 Archive unmaintained modules
 

 Key: JDO-699
 URL: https://issues.apache.org/jira/browse/JDO-699
 Project: JDO
  Issue Type: Improvement
  Components: api11, api2-legacy, btree, core2, enhancer2, fostore2, 
 model2, query2, ri11, runtime2, tck11, tck2-legacy, util2
Affects Versions: JDO 3 maintenance release 1
Reporter: Matthew T. Adams
Assignee: Matthew T. Adams
 Fix For: JDO 3 maintenance release 1


 There are many modules in the trunk of the JDO source repo that are no longer 
 maintained.  I propose to create a new directory archive as a peer to 
 trunk, branches, releases, and site, then svn-move them from trunk to archive.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (JDO-699) Archive unmaintained modules

2011-10-28 Thread Craig L Russell (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/JDO-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13138570#comment-13138570
 ] 

Craig L Russell commented on JDO-699:
-

I agree that keeping unmaintained sub-projects in trunk is not good. Moving 
them to a new archive directory makes sense. I wouldn't just delete them since 
it would then be difficult to find them.

 Archive unmaintained modules
 

 Key: JDO-699
 URL: https://issues.apache.org/jira/browse/JDO-699
 Project: JDO
  Issue Type: Improvement
  Components: api11, api2-legacy, btree, core2, enhancer2, fostore2, 
 model2, query2, ri11, runtime2, tck11, tck2-legacy, util2
Affects Versions: JDO 3 maintenance release 1
Reporter: Matthew T. Adams
Assignee: Matthew T. Adams
 Fix For: JDO 3 maintenance release 1


 There are many modules in the trunk of the JDO source repo that are no longer 
 maintained.  I propose to create a new directory archive as a peer to 
 trunk, branches, releases, and site, then svn-move them from trunk to archive.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira