You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by Michael Dick <mi...@gmail.com> on 2008/08/01 18:39:23 UTC
[VOTE] Approve OpenJPA 1.2.0 release
OpenJPA Developers,
A candidate build for OpenJPA 1.2.0 is available on
http://people.apache.org/~mikedd in the following locations.
Source archive:
http://people.apache.org/~mikedd/openjpa/1.2.0/staging-repo/org/apache/openjpa/apache-openjpa/1.2.0/apache-openjpa-1.2.0-source.zip
Binary archive:
http://people.apache.org/~mikedd/openjpa/1.2.0/staging-repo/org/apache/openjpa/apache-openjpa/1.2.0/apache-openjpa-1.2.0-binary.zip
*GPG signatures and checksums (MD5 and SHA1) can be found in the parent
directory:
http://people.apache.org/~mikedd/openjpa/1.2.0/staging-repo/org/apache/openjpa/apache-openjpa/1.2.0/
Documentation has also been published in the following locations.
Manual :
http://people.apache.org/~mikedd/openjpa/1.2.0/staging-site/apache-openjpa-1.2.0/docs/manual/
Javadoc :
http://people.apache.org/~mikedd/openjpa/1.2.0/staging-site/docs/javadoc/
Release Notes :
http://svn.apache.org/viewvc/openjpa/tags/1.2.0/openjpa-project/RELEASE-NOTES.html?revision=677734&view=markup
In addition maven artifacts have been published to a staging repository on
people.apache.org. You may use the staging repository by adding the
following information in pom.xml :
<repositories>
. . .
<repository>
<id>OpenJPA 1.2.0 staging repository</id>
<name>OpenJPA 1.2.0 staging repository</name>
<url>
http://people.apache.org/~mikedd/openjpa/1.2.0/staging-repo/
</url>
</repository>
</repositories>
. . .
<dependencies>
. . .
<dependency>
<groupId>org.apache.openjpa</groupId>
<artifactId>openjpa</artifactId>
<version>1.2.0</version>
</dependency>
</dependencies>
The Release Audit Tool maven plugin was executed with the build candidate
and no problems were found.
Please vote to publish this incubating release on the project Web page:
http://cwiki.apache.org/openjpa/downloads.html
This vote will remain open until 11:40 CDT Wednesday August 05, 2008. A "+1"
indicates that you approve of the release, a "-1" indicates a vote against
making a release.
Thanks in advance for your help in ratifying this release!
-Michael Dick
Re: [VOTE] Approve OpenJPA 1.2.0 release
Posted by Michael Dick <mi...@gmail.com>.
For the time being I've targetted OPENJPA-628 for 1.2.1. If there are
additional far reaching concerns we can address them in the JIRA issue and
decide whether it needs to be re-targetted.
-mike
On Sun, Aug 3, 2008 at 3:26 PM, Pinaki Poddar <pp...@apache.org> wrote:
>
> but can you explain your "far reaching" comment?
>
> Apologies for sounding like a 'flip-flopper' during this election session:
> My initial impression was that the change will impact adding elements to
> any detached proxy collection. If that were the case then that is a serious
> enough case to warranty a resolution. But on a second look, the impact
> seems
> to be narrower.
> Need more investigation before making any further (wrong) statement.
>
> Regards --
>
>
>
> Kevin Sutter wrote:
> >
> > I can agree that this problem (the r610922 regression) should be
> resolved,
> > but since it has been there for quite some time, does it have to be
> > resolved
> > before we complete the 1.2.0 release? I've read through the Issue
> > (OPENJPA-628) and I understand the basic problem, but can you explain
> your
> > "far reaching" comment? I'm trying to figure out whether this is
> > pervasive
> > enough to warrant a re-spin.
> >
> > Thanks,
> > Kevin
> >
> > On Sat, Aug 2, 2008 at 11:41 AM, Pinaki Poddar <pp...@apache.org>
> wrote:
> >
> >>
> >> I have earlier voted +1.
> >> But now I will like to point out that 1.2.0 should be released *after*
> >> either a) r610922 reverted
> >> or b) the regression caused by 610922 (which is far reaching via
> >> dynamically generated proxies) is resolved
> >>
> >> --
> >> View this message in context:
> >>
> http://n2.nabble.com/-VOTE--Approve-OpenJPA-1.2.0-release-tp664599p666095.html
> >> Sent from the OpenJPA Developers mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://n2.nabble.com/-VOTE--Approve-OpenJPA-1.2.0-release-tp664599p667447.html
> Sent from the OpenJPA Developers mailing list archive at Nabble.com.
>
>
Re: [VOTE] Approve OpenJPA 1.2.0 release
Posted by Pinaki Poddar <pp...@apache.org>.
but can you explain your "far reaching" comment?
Apologies for sounding like a 'flip-flopper' during this election session:
My initial impression was that the change will impact adding elements to
any detached proxy collection. If that were the case then that is a serious
enough case to warranty a resolution. But on a second look, the impact seems
to be narrower.
Need more investigation before making any further (wrong) statement.
Regards --
Kevin Sutter wrote:
>
> I can agree that this problem (the r610922 regression) should be resolved,
> but since it has been there for quite some time, does it have to be
> resolved
> before we complete the 1.2.0 release? I've read through the Issue
> (OPENJPA-628) and I understand the basic problem, but can you explain your
> "far reaching" comment? I'm trying to figure out whether this is
> pervasive
> enough to warrant a re-spin.
>
> Thanks,
> Kevin
>
> On Sat, Aug 2, 2008 at 11:41 AM, Pinaki Poddar <pp...@apache.org> wrote:
>
>>
>> I have earlier voted +1.
>> But now I will like to point out that 1.2.0 should be released *after*
>> either a) r610922 reverted
>> or b) the regression caused by 610922 (which is far reaching via
>> dynamically generated proxies) is resolved
>>
>> --
>> View this message in context:
>> http://n2.nabble.com/-VOTE--Approve-OpenJPA-1.2.0-release-tp664599p666095.html
>> Sent from the OpenJPA Developers mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://n2.nabble.com/-VOTE--Approve-OpenJPA-1.2.0-release-tp664599p667447.html
Sent from the OpenJPA Developers mailing list archive at Nabble.com.
Re: [VOTE] Approve OpenJPA 1.2.0 release
Posted by Kevin Sutter <kw...@gmail.com>.
I can agree that this problem (the r610922 regression) should be resolved,
but since it has been there for quite some time, does it have to be resolved
before we complete the 1.2.0 release? I've read through the Issue
(OPENJPA-628) and I understand the basic problem, but can you explain your
"far reaching" comment? I'm trying to figure out whether this is pervasive
enough to warrant a re-spin.
Thanks,
Kevin
On Sat, Aug 2, 2008 at 11:41 AM, Pinaki Poddar <pp...@apache.org> wrote:
>
> I have earlier voted +1.
> But now I will like to point out that 1.2.0 should be released *after*
> either a) r610922 reverted
> or b) the regression caused by 610922 (which is far reaching via
> dynamically generated proxies) is resolved
>
> --
> View this message in context:
> http://n2.nabble.com/-VOTE--Approve-OpenJPA-1.2.0-release-tp664599p666095.html
> Sent from the OpenJPA Developers mailing list archive at Nabble.com.
>
>
Re: [VOTE] Approve OpenJPA 1.2.0 release
Posted by Pinaki Poddar <pp...@apache.org>.
I have earlier voted +1.
But now I will like to point out that 1.2.0 should be released *after*
either a) r610922 reverted
or b) the regression caused by 610922 (which is far reaching via
dynamically generated proxies) is resolved
--
View this message in context: http://n2.nabble.com/-VOTE--Approve-OpenJPA-1.2.0-release-tp664599p666095.html
Sent from the OpenJPA Developers mailing list archive at Nabble.com.
Re: [VOTE] Approve OpenJPA 1.2.0 release
Posted by Pinaki Poddar <pp...@apache.org>.
+1
--
View this message in context: http://n2.nabble.com/-VOTE--Approve-OpenJPA-1.2.0-release-tp664599p664953.html
Sent from the OpenJPA Developers mailing list archive at Nabble.com.