Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (nike.apache.org: domain of kwsutter@gmail.com designates
 209.85.214.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1325700703.52139.YahooMailNeo@web114512.mail.gq1.yahoo.com>
References: <1325697081.9123.YahooMailNeo@web27807.mail.ukl.yahoo.com>
 <1325700703.52139.YahooMailNeo@web114512.mail.gq1.yahoo.com>
From: Kevin Sutter <kwsutter@gmail.com>
Date: Wed, 4 Jan 2012 12:41:23 -0600
Message-ID: 
 <CABH8er=p1OEKvVg8YgFy7=1RSLK_3T+6dKh81aY7xWSNxFiSyA@mail.gmail.com>
Subject: Re: [DISCUSS] release openjpa-2.2.0?
To: dev@openjpa.apache.org, Donald Woods <dwoods@apache.org>
Content-Type: multipart/alternative; boundary=14dae9340dd3d7b69e04b5b82abb

--14dae9340dd3d7b69e04b5b82abb
Content-Type: text/plain; charset=ISO-8859-1

Donald,

> I would suggest someone verifying a clean TCK run before we branch.
>

Excellent idea.  We used to have someone from the Apache community do this
for us since not everybody has access to the TCK.  Is there someone that
can step up to do this?


>
> Also, are there any samples or experimental code that needs to be removed
> or cleaned up before we create a 2.2.0 release?
>

Since you brought this up...  I'm think we need to re-think the JEST module
that is currently in trunk.  Pinaki originally put it into trunk with the
hopes of solidifying it before we do another release.  I don't think that
effort has transpired.  Since it's a separate module, maybe it can be
pulled before creating the 2.2.0 release and 2.2.x service stream and then
put back into trunk?  Other ideas?

Kevin


>
> -Donald
>
>
>
> ________________________________
>  From: Mark Struberg <struberg@yahoo.de>
> To: openjpa-dev <dev@openjpa.apache.org>
> Cc: David Blevins <david.blevins@gmail.com>
> Sent: Wednesday, January 4, 2012 12:11 PM
> Subject: [DISCUSS] release openjpa-2.2.0?
>
> Hi folks!
>
> I've now used openjpa-2.2.0 excessively and it looks very good to me.
> What do you think about going forward and shipping a 2.2.0?
> Or at least a RC1...
>
> OpenEJB and Geronimo are waiting for an openjpa-2.2.x release as well ;)
>
> LieGrue,
> strub
>

--14dae9340dd3d7b69e04b5b82abb--