Attendees: Michelle Caisse, Matthew Adams, Erik Bengtson, Craig Russell
Agenda:1. Moving forward with JDO maintenance release. The plan is to make an action item list of approved items from the maintenance review and determine what additional test cases need to be developed for both 1.5 and 1.3 (legacy) api and tck. Once a number of the common items have been developed, the legacy projects will be forked (svn copy) and the 1.5-only work can be done.
How to promote JDO 2.1? Maybe a ServerSide article on the differences from JDO 2.0 and perhaps a deep dive on comparing the persistence alternatives?
2. Other issuesItems for maintenance that missed the initial maintenance review can still be developed. Another maintenance review will be done for those items that we can agree on, including access to time in JDOQL queries.
Action Items from weeks past:[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate different defaults for annotations (?) based on context. In progress.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on TheServerSide directing attention to the site. T-shirts, logo. AI: Craig write a ServerSide article.
-- Michelle Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
