Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: pass (athena.apache.org: domain of kwsutter@gmail.com designates
 209.85.215.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1379860400.70221.YahooMailNeo@web28904.mail.ir2.yahoo.com>
References: 
 <CAP_uWji3NP7q10J8ZrYC4K2v_S4ht-Bg=9xu3gozc62cUhGirA@mail.gmail.com>
 <CABH8erkPaOJYqoP7viXW+HZ8knBdNDjR92oFRFgMhRs=9uayjg@mail.gmail.com>
 <1379860400.70221.YahooMailNeo@web28904.mail.ir2.yahoo.com>
From: Kevin Sutter <kwsutter@gmail.com>
Date: Mon, 23 Sep 2013 07:57:35 -0500
Message-ID: 
 <CABH8er=tvsjRP1LjOpkyQx5svzRxHc-ZdWq3HuWxtbO26OpLuA@mail.gmail.com>
Subject: Re: OpenJPA 2.3.0 Release
To: users@openjpa.apache.org, Mark Struberg <struberg@yahoo.de>
Content-Type: multipart/alternative; boundary=001a1135e1f6a3320504e70c9127

--001a1135e1f6a3320504e70c9127
Content-Type: text/plain; charset=ISO-8859-1

Thanks, 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 <struberg@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 <kwsutter@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.gavinowich@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
> >>
> >
>

--001a1135e1f6a3320504e70c9127--