Attendees: Michael Bouschen, Craig Russell NOTE: due to schedule conflicts, no meeting next week. Next meeting: Sept 12.
Agenda: 1. JIRA "Support for conditional operator ? : in JDOQL": https://issues.apache.org/jira/browse/JDO-650 Andy commented: > DataNucleus already does support "java syntax" of > IF (...) ELSE IF (...) ... ELSE ... > This was valid Java last I looked at the language doc - yes it doesn't have > RETURN when in the RESULT clause but pretty damn close. If I was writing Java > code for returning a value from a method and there was complicated logic for > what to return I would use IF ... ELSE IF ... ELSE ... rather than nested > (expr ? expr1 : (expr2 ? expr3 : (expr4 ? expr5 : expr6))). > > It doesn't currently support "(expr ? val1 : val2)" but then someone could > easily contribute support for that - whoever does it would have to be careful > when implementing it to distinguish ":" detection from explicit parameter > syntax though. We have three choices to implement this functionality : a) expr ? exprT : exprF b) IF(...) ELSE... c) SQL syntax The a syntax is Java. The b syntax is "very close to" Java but there are some cases where you can't simply copy and paste JDOQL into a Java program. So this would just be one more case. The c syntax is not very close to Java. AI Craig add a comment to the jira. 2. Allow makePersistent outside a transaction: https://issues.apache.org/jira/browse/JDO-589 no news. 3. JIRA "Modify specification to address NoSQL datastores": https://issues.apache.org/jira/browse/JDO-651 no news. 4. JDO 3.1 Andy commented: > When is there going to be an actual release process that can be followed? I > mean one that doesn't get hung up on waiting for a JCP? aka things beyond > this > projects control ? It is impossible for any downstream project to rely on > Apache JDO project as it is now ... no visibility of when things will get > released ... if ever (JDO 3.1 should have been 2012). For that reason I don't > have much time at all for what is there now, sorry. The "HowToReleaseJDO.html" document specifies how to release projects through Apache, but doesn't address how to make official JCP releases. I think this is still a good separation. As maintenance lead for JSR 243 I have worked the JCP process in parallel with the Apache release process. But I can no longer see the need for making the JCP process and Apache process parallel. So I'm proposing that we do our Apache release process for 3.1 and later push the "official Apache 3.1 release" through the JCP release process. As part of this change, we need to update the specifications page of the JDO web site http://db.apache.org/jdo/specifications.html to remove the 3.1 release from "JDO Final Specifications" since this is a term of art of the JCP. We instead should name the top part "JDO Releases Approved by JCP" and the lower part "JDO Releases Pending Approval by JCP". If needed, we can add a third part "JDO Works In Progress". 5. Other issues Action Items from weeks past: [Apr 25 2014] AI Craig update How To Release JDO document to add instructions on how to use the new svnpubsub strategy for releasing. [Feb 28 2014] AI Everyone: take a look at https://issues.apache.org/jira/browse/JDO-712 [Feb 28 2014] AI Everyone: take a look at https://issues.apache.org/jira/browse/JDO-625 [Dec 13 2013] AI Craig file a JIRA for java.sql.Blob and java.sql.Clob as persistent field types [May 10 2013] AI Everyone take a look Apache ISIS and maybe subscribe to ISIS mail lists. [Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about JDOHelper methods. In process. 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!
