Cool.
I am very much into "release often release early" philosophy, and I'd
like to start following it with 3.0 on both counts.
BTW, I just fixed a few remaining EJBQL join bugs that I found, so
now I will fully concentrate on cross-DB testing and the docs.
Andrus
On Jun 25, 2007, at 7:41 PM, Kevin Menard wrote:
I'm for it. I've been out of the 3.0 game for a little bit, but it
seemed pretty stable the last time I tried it. It'd be helpful to get
other people using it, too. Early adopters can provide plenty of JIRA
goodness.
--
Kevin
-----Original Message-----
From: Andrus Adamchik [mailto:[EMAIL PROTECTED]
Sent: Friday, June 22, 2007 9:24 AM
To: [email protected]
Subject: How about 3.0 M1?
What's the consensus on making 3.0 M1 release?
I think it is long overdue - we want to show the many things
we've developed over the last 1+ year [1]. Also I just
checked in the minimal EJBQL support so that users can play
with it (that was my own minimal TODO). As before "M"
(milestone) means an alpha quality release with unstable new
features, "unstable" indicating that the new API can change
over the course of the release.
If nobody objects to going forward with M1, I will switch in
the release preparation mode, testing the code across
different databases, writing the docs, etc.
Andrus
[1] http://cayenne.apache.org/doc/guide-to-30-features.html
