Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.de;
  h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=HWkuK1H7Bj9Zr/Q2PXhbc0fMnxlXfBMr0nym9zCACpZ8Wzz9oCiZBlnTHujKKAijEEjKkXvd4Wi+WQxWXpvVY8Z+l/iU7C75eDw7SSt9vcnc1XJdgDjv4eYmBMkcQKL5Sgd/MDhwmZrogDphm3Xni7AtbWwnoqWPJyNShU4IaY4=;
References: <1325697081.9123.YahooMailNeo@web27807.mail.ukl.yahoo.com>
 <1325700703.52139.YahooMailNeo@web114512.mail.gq1.yahoo.com>
 <CABH8er=p1OEKvVg8YgFy7=1RSLK_3T+6dKh81aY7xWSNxFiSyA@mail.gmail.com>
 <1325704269.65365.YahooMailNeo@web27807.mail.ukl.yahoo.com>
 <1325851309.17440.YahooMailNeo@web27808.mail.ukl.yahoo.com>
 <CABH8ermtZ=NqJGdWtJSDiMtD7TFxsSBGQsWKuUAHjvxEW-dWDA@mail.gmail.com>
 <CAON=uekEWWMz0yWVC-QyOpAgRa4W_=OOkyAyYfcCcBrW=Pt3xg@mail.gmail.com>
Message-ID: <1325887706.9589.YahooMailNeo@web27802.mail.ukl.yahoo.com>
Date: Fri, 6 Jan 2012 22:08:26 +0000 (GMT)
From: Mark Struberg <struberg@yahoo.de>
Reply-To: Mark Struberg <struberg@yahoo.de>
Subject: Re: [DISCUSS] release openjpa-2.2.0?
To: "dev@openjpa.apache.org" <dev@openjpa.apache.org>
In-Reply-To: 
 <CAON=uekEWWMz0yWVC-QyOpAgRa4W_=OOkyAyYfcCcBrW=Pt3xg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Albert!=0AI have no special interrest in maintaining this branch longer =
as needed. I'm just a user like anyone else. =0A=0AThe main reason for push=
ing this release is that the last OpenJPA release was pretty long time ago =
and trunk already contains quite a few important improvements.=0A=0AIn Open=
WebBeans and MyFaces we usually only create a new maintenance branch if the=
re were big new features to be incorporated in trunk. If we know that we li=
ke to do a new heavyweight feature, then we create a branch for 2.2.x and d=
o the maintenance there. Otherwise we release from trunk because we don't l=
ike to do all the merging stuff if not really needed.=0A=0ABut I'm fine wit=
h whatever branching behaviour the OpenJPA community is used to (just need =
to know it).=0A=0A=0ALieGrue,=0Astrub=0A=A0=0A=0A=0A=0A----- Original Messa=
ge -----=0A> From: Albert Lee <allee8285@gmail.com>=0A> To: dev@openjpa.apa=
che.org=0A> Cc: =0A> Sent: Friday, January 6, 2012 6:41 PM=0A> Subject: Re:=
 [DISCUSS] release openjpa-2.2.0?=0A> =0A> Mark,=0A> =0A> You are advocatin=
g a 2.2.x maintenance release. Per Kevin's note on service=0A> branch manag=
ement, do you have a need to "own" that release for your=0A> product servic=
ing need?=0A> =0A> We have the same service requirement based on trunk righ=
t now. If you need=0A> owning the 2.2.1 service branch, we can create a sep=
arate 2.2.2 after 2.2.1=0A> is completed. Otherwise we can be the release o=
wner of the 2.2.1 branch.=0A> =0A> Albert Lee.=0A> =0A> On Fri, Jan 6, 2012=
 at 10:02 AM, Kevin Sutter <kwsutter@gmail.com> wrote:=0A> =0A>>  Hi Mark,=
=0A>>  You're on the right track.=A0 You can browse the OpenJPA svn reposit=
ory =0A> to=0A>>  see how we've done it in the past.=A0 For example, each o=
f our major =0A> releases=0A>>  is always tagged:=0A>> =0A>>  https://svn.a=
pache.org/repos/asf/openjpa/tags=0A>> =0A>>  And, corresponding to most of =
these releases is a service branch:=0A>> =0A>>  https://svn.apache.org/repo=
s/asf/openjpa/branches=0A>> =0A>>  Mainline development continues on trunk.=
=A0 So, once we cut the 2.2.0=0A>>  release, then trunk becomes 2.3.0-SNAPS=
HOT.=A0 That is, trunk is working=0A>>  towards the next 2.3.0 release.=0A>=
> =0A>>  Each of the service branches has an owning manager.=A0 That manage=
r normally=0A>>  creates and maintains that service branch.=A0 Nothing goes=
 into that service=0A>>  branch without the owning manager's signoff.=0A>> =
=0A>>  This approach allows multiple organizations to own their service bra=
nches,=0A>>  if desired.=A0 So, after the 2.2.0 release is complete, we nor=
mally create=0A>>  the 2.2.x service branch.=A0 But, if there is a reason f=
or you to maintain a=0A>>  2.2.0-mt service branch, there is nothing stoppi=
ng you.=A0 It's quite=0A>>  flexible.=0A>> =0A>>  At some point, there may =
be a determination to also create a service=0A>>  release off the branch.=
=A0 For example, you'll notice that we have =0A> created a=0A>>  2.1.1 rele=
ase based off the 2.1.x service branch.=0A>> =0A>>  Make sense?=A0 This is =
the approach we have used for several releases and=0A>>  it's been working =
for the OpenJPA development team.=0A>> =0A>>  Here are a few links that hel=
p describe our process:=0A>>  http://openjpa.apache.org/release-management.=
html=0A>>  http://openjpa.apache.org/openjpa-release-policy.html=0A>> =0A>>=
  Kevin=0A>> =0A>>  On Fri, Jan 6, 2012 at 6:01 AM, Mark Struberg <struberg=
@yahoo.de> =0A> wrote:=0A>> =0A>>  > To not let this slip.=0A>>  >=0A>>  >=
=0A>>  > What are the release plans in general? Do you like to start with t=
he =0A> work=0A>>  > on the new JPA spec soon (guess this might take anothe=
r year to get=0A>>  > finished). I'd rather keep the trunk as main developm=
ent stage and =0A> would=0A>>  > like to work towards a 2.2.1 afterwards on=
 trunk.=0A>>  >=0A>>  > The reason why I ask this is for the branch we like=
 to create. =0A> It's a=0A>>  > difference if we just create a '2.2.0-mt' b=
ranch (mt for =0A> maintenance)=0A>>  only=0A>>  > for getting 2.2.0 out of=
 the door, and continue our main development=0A>>  effort=0A>>  > on trunk.=
 Or if we create a '2.2.x' branch and do the most =0A> work there=0A>>  (an=
d=0A>>  > need to merge all work over to trunk).=0A>>  >=0A>>  > I'm +1 for=
 2.2.0-mt=0A>>  >=0A>>  > If noone objects then I like to start this new br=
anch middle of next=0A>>  week.=0A>>  > What work needs to be done until th=
en? My gut feeling says:=0A>>  >=0A>>  > * review open JIRAs=0A>>  >=A0  * =
verify and resolve the ones already fixed=0A>>  >=A0  * update the fix-vers=
ion to 2.2.1 for the others=0A>>  > * run the TCK=0A>>  > * verify/update t=
he documentation of new features.=0A>>  >=0A>>  > This reminds me that our =
pdf doesn't contain good information for =0A> the new=0A>>  > openjpa-maven=
-plugin. I was also not able to find where we deploy the=0A>>  > plugin doc=
umentation to. This is imo something we should review/fix=0A>>  before=0A>>=
  > we branch.=0A>>  >=0A>>  >=0A>>  > feel free to add missing tasks.=0A>>=
  >=0A>>  >=0A>>  >=0A>>  > LieGrue,=0A>>  > strub=0A>>  >=0A>>  >=0A>>  >=
=0A>>  > ----- Original Message -----=0A>>  > > From: Mark Struberg <strube=
rg@yahoo.de>=0A>>  > > To: "dev@openjpa.apache.org" =0A> <dev@openjpa.apach=
e.org>=0A>>  > > Cc:=0A>>  > > Sent: Wednesday, January 4, 2012 8:11 PM=0A>=
>  > > Subject: Re: [DISCUSS] release openjpa-2.2.0?=0A>>  > >=0A>>  > > I'=
d just branch the trunk and remove JEST later. Or just keep =0A> it and=0A>=
>  > mark it=0A>>  > > as 'experimental' - doesn't hurt!=0A>>  > >=0A>>  > =
> LieGrue,=0A>>  > > strub=0A>>  > >=0A>>  > >=0A>>  > >=0A>>  > > ----- Or=
iginal Message -----=0A>>  > >>=A0 From: Kevin Sutter <kwsutter@gmail.com>=
=0A>>  > >>=A0 To: dev@openjpa.apache.org; Donald Woods =0A> <dwoods@apache=
.org>=0A>>  > >>=A0 Cc:=0A>>  > >>=A0 Sent: Wednesday, January 4, 2012 7:41=
 PM=0A>>  > >>=A0 Subject: Re: [DISCUSS] release openjpa-2.2.0?=0A>>  > >>=
=0A>>  > >>=A0 Donald,=0A>>  > >>=0A>>  > >>>=A0  I would suggest someone v=
erifying a clean TCK run =0A> before we branch.=0A>>  > >>>=0A>>  > >>=0A>>=
  > >>=A0 Excellent idea.=A0 We used to have someone from the Apache =0A> c=
ommunity do=0A>>  > this=0A>>  > >>=A0 for us since not everybody has acces=
s to the TCK.=A0 Is there =0A> someone=0A>>  > that=0A>>  > >>=A0 can step =
up to do this?=0A>>  > >>=0A>>  > >>=0A>>  > >>>=0A>>  > >>>=A0  Also, are =
there any samples or experimental code that =0A> needs to be=0A>>  > > remo=
ved=0A>>  > >>>=A0  or cleaned up before we create a 2.2.0 release?=0A>>  >=
 >>>=0A>>  > >>=0A>>  > >>=A0 Since you brought this up...=A0 I'm think we =
need to =0A> re-think the JEST=0A>>  > > module=0A>>  > >>=A0 that is curre=
ntly in trunk.=A0 Pinaki originally put it into =0A> trunk with=0A>>  > the=
=0A>>  > >>=A0 hopes of solidifying it before we do another release.=A0 I =
=0A> don't think=0A>>  > > that=0A>>  > >>=A0 effort has transpired.=A0 Sin=
ce it's a separate module, =0A> maybe it can be=0A>>  > >>=A0 pulled before=
 creating the 2.2.0 release and 2.2.x service =0A> stream and=0A>>  > then=
=0A>>  > >>=A0 put back into trunk?=A0 Other ideas?=0A>>  > >>=0A>>  > >>=
=A0 Kevin=0A>>  > >>=0A>>  > >>=0A>>  > >>>=0A>>  > >>>=A0  -Donald=0A>>  >=
 >>>=0A>>  > >>>=0A>>  > >>>=0A>>  > >>>=A0  ______________________________=
__=0A>>  > >>>=A0 =A0 From: Mark Struberg <struberg@yahoo.de>=0A>>  > >>>=
=A0  To: openjpa-dev <dev@openjpa.apache.org>=0A>>  > >>>=A0  Cc: David Ble=
vins <david.blevins@gmail.com>=0A>>  > >>>=A0  Sent: Wednesday, January 4, =
2012 12:11 PM=0A>>  > >>>=A0  Subject: [DISCUSS] release openjpa-2.2.0?=0A>=
>  > >>>=0A>>  > >>>=A0  Hi folks!=0A>>  > >>>=0A>>  > >>>=A0  I've now use=
d openjpa-2.2.0 excessively and it =0A> looks very good to=0A>>  > > me.=0A=
>>  > >>>=A0  What do you think about going forward and shipping a =0A> 2.2=
.0?=0A>>  > >>>=A0  Or at least a RC1...=0A>>  > >>>=0A>>  > >>>=A0  OpenEJ=
B and Geronimo are waiting for an openjpa-2.2.x =0A> release as=0A>>  well=
=0A>>  > > ;)=0A>>  > >>>=0A>>  > >>>=A0  LieGrue,=0A>>  > >>>=A0  strub=0A=
>>  > >>>=0A>>  > >>=0A>>  > >=0A>>  >=0A>> =0A> =0A> =0A> =0A> -- =0A> Alb=
ert Lee.=0A>