Everything is a go from the Geronimo side, as we got a clean TCK run
completed. Can we start a OpenJPA 1.2.1 release now?
Thanks,
-Donald
Donald Woods wrote:
Mike, it looks like all of our TCK failures related to JPA have been
fixed and verified. Can you start the process of cutting a 1.2.1 branch
while we finish our TCK runs? I'd still wait until we have the
complete results in (probably sometime Friday) before you start a RC vote.
Thanks,
Donald
Michael Dick wrote:
Hi Kevan,
I've been planning on doing a 1.2.1 release "real soon now" for a while.
I'll start working on it later this week (early next week at the latest).
Regards,
-mike
On Tue, Jan 27, 2009 at 11:04 AM, Kevan Miller
<[email protected]>wrote:
Thanks Kevin and Jeremy for helping to resolve OPENJPA-872.
Is there an outlook for an OpenJPA 1.2.1 release? Geronimo is going
to need
a release prior to releasing Geronimo 2.1.4 and 2.2. I guess we could
consider using openjpa.jdbc.QuerySQLCache=false as a work-around, but
I'd
rather avoid that... Meantime, we'll start using 1.2.1-SNAPSHOT
--kevan
