Attendees: Michelle Caisse, Matthew Adams, Craig Russell
Agenda:1. JDO 2.2 plans: Craig sent mail soliciting input for the release. A few responses so far. Can we have a shorter release cycle? Perhaps 3 to 6 months.
Items suggested for this release include: Dynamic fetch plans (also add method setRecursionDepth on FetchPlan) Service Loader pattern for JDOHelper.getPersistenceManagerFactory Add new constructors for exceptions Support for multiple datastores JMX management/monitoring model OSGi Service (Similar to JDO-556) The long awaited enhancer API Schema synchronization API (generates/modifies schema) level of standardisation of transaction isolationAI Everyone who proposed a feature, please add a JIRA issue and assign it to a volunteer who will implement the feature. Discussion can then continue around the JIRA issues.
2. Plan to promote JDO 2.1. AI Craig write up a release announcement for posting to Apache, ServerSide, etc.
Action Items from weeks past:[Feb 1 2008] AI Matthew see what would be needed to update the PMF contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query for post-JDO 2.1.
[May 25 2007] AI everyone download the Grails demo from grails.org and check it out. Also look at Grails/Groovy ExpandoMetaClass that has the magic to avoid reflection and enhancement.
[May 25 2007] AI Matthew Adams prepare a proposal with just the basics of schema synchronization with jdo and orm metadata.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide directing attention to the site. T-shirts. 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
