Hi Mark,
My original proposal [1] was to cut this OpenJPA 2.3.0 release and then do
JPA 2.1 in trunk.  Trunk would become 3.0.0-SNAPSHOT.  We do have an
existing JPA 2.1 sandbox, but we would merge the work that Pinaki has done
into trunk -- after we cut off the 2.3.0 release.  That would be the plan
anyway.

Kevin

[1]
http://openjpa.208410.n2.nabble.com/JPA-2-1-Development-Kickoff-td7584933.html


On Wed, Oct 2, 2013 at 12:58 AM, Mark Struberg <strub...@yahoo.de> wrote:

> Well, actually the most important thing in this release is the ASM4 fix.
> I plan to do much more releases on a much tighter schedule. We should get
> out bugfixes much quicker imo.
>
> I 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?
> Just for me to understand how much work is done in which place...
>
> LieGrue,
> strub
>
>
>
>
> ----- Original Message -----
> > From: Kevin Sutter <kwsut...@gmail.com>
> > To: users@openjpa.apache.org; Mark Struberg <strub...@yahoo.de>;
> d...@openjpa.apache.org
> > Cc:
> > Sent: Monday, 30 September 2013, 18:31
> > Subject: Re: OpenJPA 2.3.0 Release
> >
> > I think we need to get this out to the dev community as well...  Have you
> > done any triage on the existing JIRAs for any show-stoppers?
> >
> > Thanks,
> > Kevin
> >
> >
> > On Sat, Sep 28, 2013 at 7:22 AM, Mark Struberg <strub...@yahoo.de>
> wrote:
> >
> >>  I've now created the 2.3.x branch for preparing the release.
> >>  If you find any showstoppers in trunk then please think about pinging
> me.
> >>
> >>  LieGrue,
> >>  strub
> >>
> >>
> >>
> >>
> >>  ----- Original Message -----
> >>  > From: Kevin Sutter <kwsut...@gmail.com>
> >>  > To: users@openjpa.apache.org; Mark Struberg <strub...@yahoo.de>
> >>  > Cc:
> >>  > Sent: Monday, 23 September 2013, 14:57
> >>  > Subject: Re: OpenJPA 2.3.0 Release
> >>  >
> >>  >T hanks, Mark.
> >>  >
> >>  > Here's a starting point for our release process:
> >>  > http://openjpa.apache.org/release-management.html
> >>  >
> >>  > The steps you are interested in are under the Apache Nexus Release
> >>  > process:
> >>  >
> >>
> http://openjpa.apache.org/apache-nexus-release-process-(1.2.x-2.1.x).html
> >>  >
> >>  > Good luck!  There are several people that have done Apache OpenJPA
> >>  releases
> >>  > recently, so hopefully you'll get the assistance you need.  But, I
> > do
> >>  know
> >>  > at least one of them is busy with JavaOne this week...
> >>  >
> >>  > Kevin
> >>  >
> >>  >
> >>  > On Sun, Sep 22, 2013 at 9:33 AM, Mark Struberg
> > <strub...@yahoo.de>
> >>  wrote:
> >>  >
> >>  >>  I can kick off all the maven parts of the release.
> >>  >>
> >>  >>  I'm not sure what else do we need in terms of readme and JISA
> > release
> >>  >>  notes housekeeping?
> >>  >>  Is there a wiki page or any other documentation about it
> > somewhere?
> >>  >>
> >>  >>  From my experience as Release Manager in other Apache projects I
> > would
> >>  >>  have the following tasks on my TODO list. And some of them need
> >>  community
> >>  >>  involvement prior to starting the actual release process
> >>  >>
> >>  >>  * go through all open JIRA issues which have 2.3 as target
> > release.
> >>  There
> >>  >>  might be some of them which already got released. Then do the
> > same for
> >>  all
> >>  >>  open issues which show no apparent target version.
> >>  >>  * Check all resolved issues and file them into release notes.
> >>  >>  * pick some low hanging fruits in terms of open tasks and resolve
> > them
> >>  if
> >>  >>  possible.
> >>  >>  * run the TCK. As the current 2.3.0-SNAPSHOT is daily run by the
> > TomEE
> >>  >>  build, I assume this is already covered. Please not that while
> > I'm JCP
> >>  >>  member, I have not yet filed any JPA TCK NDA. So I cannot check
> > this
> >>  myself
> >>  >>  * create a 2.3.x maintenance branch.
> >>  >>
> >>  >>  Any other tasks prior to firing up mvn release:prepare?
> >>  >>
> >>  >>
> >>  >>  LieGrue,
> >>  >>  strub
> >>  >>
> >>  >>
> >>  >>
> >>  >>
> >>  >>  ----- Original Message -----
> >>  >>  > From: Kevin Sutter <kwsut...@gmail.com>
> >>  >>  > To: users@openjpa.apache.org
> >>  >>  > Cc:
> >>  >>  > Sent: Saturday, 21 September 2013, 23:10
> >>  >>  > Subject: Re: OpenJPA 2.3.0 Release
> >>  >>  >
> >>  >>  > Hi Matias,
> >>  >>  > Yes, we have plans for a 2.3.0 release.  I just don't
> > know the
> >>  > exact
> >>  >>  dates
> >>  >>  > yet.  We need to cut a "final" major release for
> > the JPA 2.0
> >>  > level of
> >>  >>  > functionality before we kick off the JPA 2.1 development
> > activities.
> >>  > I'm
> >>  >>  > drafting a note to solicit for volunteers for this
> > activity.  I would
> >>  >>  hope
> >>  >>  > that this 2.3.0 release could be something that one of our
> > committers
> >>  >>  could
> >>  >>  > pickup rather quickly...
> >>  >>  >
> >>  >>  > Kevin
> >>  >>  >
> >>  >>  >
> >>  >>  > On Mon, Aug 26, 2013 at 1:12 PM, Matias G
> >>  >>  > <matias.gavinow...@gmail.com>wrote:
> >>  >>  >
> >>  >>  >>  Hi,
> >>  >>  >>
> >>  >>  >>  I was wondering if anyone knows whether the 2.3.0 is
> > planned and
> >>  > what
> >>  >>  would
> >>  >>  >>  the expected timeframe for that? I am very interested
> > in the fix
> >>  > for
> >>  >>  one
> >>  >>  >>  particular issue
> >>  > (https://issues.apache.org/jira/browse/OPENJPA-2318)
> >>  >>  >>  which
> >>  >>  >>  was solved just a few days ago.
> >>  >>  >>
> >>  >>  >>  I upgraded to 2.3.0-SNAPSHOT and it works for me, but
> > would find
> >>  > it
> >>  >>  really
> >>  >>  >>  helpful to know if there is a final release planned so
> > I can in
> >>  > turn
> >>  >>  plan
> >>  >>  >>  in advance for how long I could expect to keep using
> > snapshot
> >>  > versions.
> >>  >>  >>
> >>  >>  >>  I looked at previous release dates and found
> > they've happened
> >>  >>  >>  February-November-April, so I don't know if the
> > next one
> >>  > would be
> >>  >>  > happening
> >>  >>  >>  this year. In my search through the site I could not
> > find info on
> >>  >>  future
> >>  >>  >>  releases.
> >>  >>  >>
> >>  >>  >>  If anyone can point me to the right
> > resource/person/information,
> >>  > many
> >>  >>  >>  thanks.
> >>  >>  >>
> >>  >>  >>  Matias
> >>  >>  >>
> >>  >>  >
> >>  >>
> >>  >
> >>
> >
>

Reply via email to