Hi All, Recently the test suite on PostgreSQL got a few new failures related to auto-increment columns, probably after introducing delimiter support. I have communicated the details to Jeremy.
Also, OPENJPA-1289 seems to be resolved. Regards, Milosz > I'd also like to see OPENJPA-1410 make it into the release. This bug > prevents OpenJPA 2.0 from running in some environments. Donald and I have > been looking into the problem and it is tagged as critical. > > -Jeremy > > On Tue, Jan 19, 2010 at 11:44 AM, Michael Dick > <[email protected]>wrote: > > > There's also the issue of WriteBehind support (OPENJPA-1150). This work > > never got to the point where I'd be really comfortable including it in > > 2.0.0. 2.1.0 would be a better target though and I'm inclined to back out > > the code for the upcoming release. > > > > -mike > > > > > > On Tue, Jan 19, 2010 at 11:15 AM, Kevin Sutter <[email protected]> wrote: > > > > > Hi Donald, > > > I'd like to get the default settings for the DataCache figured out before > > > we > > > cut a 2.0 release [1]. We've been running with this turned "on" for our > > > performance benchmarks, so why not have this as our default? I'm running > > > our JUnit bucket as we speak... > > > > > > Thanks, > > > Kevin > > > > > > [1] https://issues.apache.org/jira/browse/OPENJPA-1469 > > > > > > On Mon, Jan 18, 2010 at 9:57 PM, Donald Woods <[email protected]> wrote: > > > > > > > We're in pretty good shape for a 2.0.0 release. > > > > Trunk is passing the JPA 2.0 TCK. > > > > We have the broadest/best junit results over Derby, DB2, Oracle, MySQL > > > > and MS SQL as we have for any release. > > > > > > > > Now, we could either release a Milestone 4 release and continue to work > > > > on docs, samples, performance and the backlog issues or we could go > > > > ahead and plan on cutting a 2.0.0 branch later this week with plans to > > > > continue improving the 2.0 codebase in maintenance releases at least > > > > every quarter. > > > > > > > > If you have any critical issues that you feel need to be resolved > > before > > > > we release 2.0.0, please update the JIRA Fix Version to 2.0.0 and set > > > > the Priority, along with replying to this discussion thread with the > > > > details of the issues you would like considered. After a couple days > > of > > > > discussions, we'll revisit the open issues and decide on which route to > > > > take. > > > > > > > > > > > > Thanks, > > > > Donald > > > > > > > > > >
