Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.de;
  h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=uK7rSbMJc9JbETnytF8W2VgB/XyvNNC0VU1QOM2b4Vb/RJMyn+WZeZglcCBGMKHnWKrdiwbA5tXDR+ZxKCAAElhEoqh9bGQ/Ug5MQcKlzKXgoN4F++eM/rtern5ZdiikrxaEzLN3hM7zXx4eLUlP4sRaEicEPJkqJWxzsJTjLTc=;
References: 
 <CAP_uWji3NP7q10J8ZrYC4K2v_S4ht-Bg=9xu3gozc62cUhGirA@mail.gmail.com>
 <CABH8erkPaOJYqoP7viXW+HZ8knBdNDjR92oFRFgMhRs=9uayjg@mail.gmail.com>
 <1379860400.70221.YahooMailNeo@web28904.mail.ir2.yahoo.com>
 <CABH8er=tvsjRP1LjOpkyQx5svzRxHc-ZdWq3HuWxtbO26OpLuA@mail.gmail.com>
 <1380370943.98745.YahooMailNeo@web28906.mail.ir2.yahoo.com>
 <CABH8ermFYkPO_L_EpunwtsrvTQCGk0g=nh0c_Gj9_F1MunaXiw@mail.gmail.com>
Message-ID: <1380693501.63087.YahooMailNeo@web28901.mail.ir2.yahoo.com>
Date: Wed, 2 Oct 2013 06:58:21 +0100 (BST)
From: Mark Struberg <struberg@yahoo.de>
Reply-To: Mark Struberg <struberg@yahoo.de>
Subject: Re: OpenJPA 2.3.0 Release
To: "dev@openjpa.apache.org" <dev@openjpa.apache.org>,
  "users@openjpa.apache.org" <users@openjpa.apache.org>
In-Reply-To: 
 <CABH8ermFYkPO_L_EpunwtsrvTQCGk0g=nh0c_Gj9_F1MunaXiw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Well, actually the most important thing in this release is the ASM4 fix.=0A=
I plan to do much more releases on a much tighter schedule. We should get o=
ut bugfixes much quicker imo.=0A=0AI suspect that JPA-2.1 work is done in a=
 branch for now and will finally end up being a 3.0.x release, right?=0AJus=
t for me to understand how much work is done in which place...=0A=0ALieGrue=
,=0Astrub=0A=0A=0A=0A=0A----- Original Message -----=0A> From: Kevin Sutter=
 <kwsutter@gmail.com>=0A> To: users@openjpa.apache.org; Mark Struberg <stru=
berg@yahoo.de>; dev@openjpa.apache.org=0A> Cc: =0A> Sent: Monday, 30 Septem=
ber 2013, 18:31=0A> Subject: Re: OpenJPA 2.3.0 Release=0A> =0A> I think we =
need to get this out to the dev community as well...=A0 Have you=0A> done a=
ny triage on the existing JIRAs for any show-stoppers?=0A> =0A> Thanks,=0A>=
 Kevin=0A> =0A> =0A> On Sat, Sep 28, 2013 at 7:22 AM, Mark Struberg <strube=
rg@yahoo.de> wrote:=0A> =0A>>  I've now created the 2.3.x branch for prepar=
ing the release.=0A>>  If you find any showstoppers in trunk then please th=
ink about pinging me.=0A>> =0A>>  LieGrue,=0A>>  strub=0A>> =0A>> =0A>> =0A=
>> =0A>>  ----- Original Message -----=0A>>  > From: Kevin Sutter <kwsutter=
@gmail.com>=0A>>  > To: users@openjpa.apache.org; Mark Struberg <struberg@y=
ahoo.de>=0A>>  > Cc:=0A>>  > Sent: Monday, 23 September 2013, 14:57=0A>>  >=
 Subject: Re: OpenJPA 2.3.0 Release=0A>>  >=0A>>  >T hanks, Mark.=0A>>  >=
=0A>>  > Here's a starting point for our release process:=0A>>  > http://op=
enjpa.apache.org/release-management.html=0A>>  >=0A>>  > The steps you are =
interested in are under the Apache Nexus Release=0A>>  > process:=0A>>  >=
=0A>>  http://openjpa.apache.org/apache-nexus-release-process-(1.2.x-2.1.x)=
.html=0A>>  >=0A>>  > Good luck!=A0 There are several people that have done=
 Apache OpenJPA=0A>>  releases=0A>>  > recently, so hopefully you'll get th=
e assistance you need.=A0 But, I =0A> do=0A>>  know=0A>>  > at least one of=
 them is busy with JavaOne this week...=0A>>  >=0A>>  > Kevin=0A>>  >=0A>> =
 >=0A>>  > On Sun, Sep 22, 2013 at 9:33 AM, Mark Struberg =0A> <struberg@ya=
hoo.de>=0A>>  wrote:=0A>>  >=0A>>  >>=A0 I can kick off all the maven parts=
 of the release.=0A>>  >>=0A>>  >>=A0 I'm not sure what else do we need in =
terms of readme and JISA =0A> release=0A>>  >>=A0 notes housekeeping?=0A>> =
 >>=A0 Is there a wiki page or any other documentation about it =0A> somewh=
ere?=0A>>  >>=0A>>  >>=A0 From my experience as Release Manager in other Ap=
ache projects I =0A> would=0A>>  >>=A0 have the following tasks on my TODO =
list. And some of them need=0A>>  community=0A>>  >>=A0 involvement prior t=
o starting the actual release process=0A>>  >>=0A>>  >>=A0 * go through all=
 open JIRA issues which have 2.3 as target =0A> release.=0A>>  There=0A>>  =
>>=A0 might be some of them which already got released. Then do the =0A> sa=
me for=0A>>  all=0A>>  >>=A0 open issues which show no apparent target vers=
ion.=0A>>  >>=A0 * Check all resolved issues and file them into release not=
es.=0A>>  >>=A0 * pick some low hanging fruits in terms of open tasks and r=
esolve =0A> them=0A>>  if=0A>>  >>=A0 possible.=0A>>  >>=A0 * run the TCK. =
As the current 2.3.0-SNAPSHOT is daily run by the =0A> TomEE=0A>>  >>=A0 bu=
ild, I assume this is already covered. Please not that while =0A> I'm JCP=
=0A>>  >>=A0 member, I have not yet filed any JPA TCK NDA. So I cannot chec=
k =0A> this=0A>>  myself=0A>>  >>=A0 * create a 2.3.x maintenance branch.=
=0A>>  >>=0A>>  >>=A0 Any other tasks prior to firing up mvn release:prepar=
e?=0A>>  >>=0A>>  >>=0A>>  >>=A0 LieGrue,=0A>>  >>=A0 strub=0A>>  >>=0A>>  =
>>=0A>>  >>=0A>>  >>=0A>>  >>=A0 ----- Original Message -----=0A>>  >>=A0 >=
 From: Kevin Sutter <kwsutter@gmail.com>=0A>>  >>=A0 > To: users@openjpa.ap=
ache.org=0A>>  >>=A0 > Cc:=0A>>  >>=A0 > Sent: Saturday, 21 September 2013,=
 23:10=0A>>  >>=A0 > Subject: Re: OpenJPA 2.3.0 Release=0A>>  >>=A0 >=0A>> =
 >>=A0 > Hi Matias,=0A>>  >>=A0 > Yes, we have plans for a 2.3.0 release.=
=A0 I just don't =0A> know the=0A>>  > exact=0A>>  >>=A0 dates=0A>>  >>=A0 =
> yet.=A0 We need to cut a "final" major release for =0A> the JPA 2.0=0A>> =
 > level of=0A>>  >>=A0 > functionality before we kick off the JPA 2.1 deve=
lopment =0A> activities.=0A>>  > I'm=0A>>  >>=A0 > drafting a note to solic=
it for volunteers for this =0A> activity.=A0 I would=0A>>  >>=A0 hope=0A>> =
 >>=A0 > that this 2.3.0 release could be something that one of our =0A> co=
mmitters=0A>>  >>=A0 could=0A>>  >>=A0 > pickup rather quickly...=0A>>  >>=
=A0 >=0A>>  >>=A0 > Kevin=0A>>  >>=A0 >=0A>>  >>=A0 >=0A>>  >>=A0 > On Mon,=
 Aug 26, 2013 at 1:12 PM, Matias G=0A>>  >>=A0 > <matias.gavinowich@gmail.c=
om>wrote:=0A>>  >>=A0 >=0A>>  >>=A0 >>=A0 Hi,=0A>>  >>=A0 >>=0A>>  >>=A0 >>=
=A0 I was wondering if anyone knows whether the 2.3.0 is =0A> planned and=
=0A>>  > what=0A>>  >>=A0 would=0A>>  >>=A0 >>=A0 the expected timeframe fo=
r that? I am very interested =0A> in the fix=0A>>  > for=0A>>  >>=A0 one=0A=
>>  >>=A0 >>=A0 particular issue=0A>>  > (https://issues.apache.org/jira/br=
owse/OPENJPA-2318)=0A>>  >>=A0 >>=A0 which=0A>>  >>=A0 >>=A0 was solved jus=
t a few days ago.=0A>>  >>=A0 >>=0A>>  >>=A0 >>=A0 I upgraded to 2.3.0-SNAP=
SHOT and it works for me, but =0A> would find=0A>>  > it=0A>>  >>=A0 really=
=0A>>  >>=A0 >>=A0 helpful to know if there is a final release planned so =
=0A> I can in=0A>>  > turn=0A>>  >>=A0 plan=0A>>  >>=A0 >>=A0 in advance fo=
r how long I could expect to keep using =0A> snapshot=0A>>  > versions.=0A>=
>  >>=A0 >>=0A>>  >>=A0 >>=A0 I looked at previous release dates and found =
=0A> they've happened=0A>>  >>=A0 >>=A0 February-November-April, so I don't=
 know if the =0A> next one=0A>>  > would be=0A>>  >>=A0 > happening=0A>>  >=
>=A0 >>=A0 this year. In my search through the site I could not =0A> find i=
nfo on=0A>>  >>=A0 future=0A>>  >>=A0 >>=A0 releases.=0A>>  >>=A0 >>=0A>>  =
>>=A0 >>=A0 If anyone can point me to the right =0A> resource/person/inform=
ation,=0A>>  > many=0A>>  >>=A0 >>=A0 thanks.=0A>>  >>=A0 >>=0A>>  >>=A0 >>=
=A0 Matias=0A>>  >>=A0 >>=0A>>  >>=A0 >=0A>>  >>=0A>>  >=0A>> =0A>