You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by Craig L Russell <Cr...@Sun.COM> on 2006/11/21 18:55:15 UTC

Branch or tag?

Hi Kevin,

It's my understanding as well that there's no difference between a  
branch and a tag from the svn perspective.

I'd like to see the tag created only after we release, if at all. The  
question for me is whether we would ever change the branch for 0.9.6  
after we release it. If not, then I agree that there is no need for a  
tag as well.

But to take perhaps a more interesting sequence, let's say we release  
OpenJPA 1.1. We create the 1.1 branch and release it, while changing  
the trunk to be 1.2-SNAPSHOT. Now we have a bunch of bug fixes for  
1.1 and want to release a 1.1.1. We have a choice between a) doing  
the bug fixing on the 1.1 branch itself and creating the 1.1.1 branch  
when we want to release 1.1.1; OR b) create the 1.1.1 branch  
immediately after releasing the 1.1 branch.

With a, we need to tag the 1.1 branch before applying any bug fixes.  
With b, we don't need to tag but have to remember that any bug fixes  
should be applied to 1.1.1 branch instead of the 1.1 branch.

Craig

On Nov 21, 2006, at 8:16 AM, Kevin Sutter wrote:

> Marc,
> +1 for the 0.9.6 release
>
> Question though...  Since tags and branches are virtually the same  
> thing in
> SVN, do we really need to have both the tagged version and the  
> branch?  It
> seems that the branch would be sufficient and then just remove the  
> tags
> folder altogether.  Unless I am missing some aspect of the tag that  
> you are
> taking advantage of...
>
> Kevin
>
>
> On 11/20/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
>>
>> OpenJPA People-
>>
>> In accordance with the Incubating Releases guidelines at  http://
>> incubator.apache.org/incubation/Incubation_Policy.html#Releases , I'd
>> like to take a third shot at making an OpenJPA release and start a
>> vote on publishing a "0.9.6-incubating" release of OpenJPA. The last
>> couple votes failed due to some problems with the notice file and
>> some source files that were missing license headers and other
>> miscellaneous issues.
>>
>> The release candidate is at:
>>
>> http://people.apache.org/repo/m2-incubating-repository/org/apache/
>> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
>> incubating-binary.zip
>>
>> The GPG signature and MD5 checksums are at:
>>
>>   http://people.apache.org/repo/m2-incubating-repository/org/apache/
>> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
>> incubating-binary.zip.asc
>>   http://people.apache.org/repo/m2-incubating-repository/org/apache/
>> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
>> incubating-binary.zip.md5
>>
>> The sources, sources GPG signature and sources MD5 checksum are
>> available at:
>>
>>   http://people.apache.org/repo/m2-incubating-repository/org/apache/
>> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
>> incubating-source.zip
>>   http://people.apache.org/repo/m2-incubating-repository/org/apache/
>> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
>> incubating-source.zip.asc
>>   http://people.apache.org/repo/m2-incubating-repository/org/apache/
>> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
>> incubating-source.zip.md5
>>
>> This build was cut from the branch at:
>>
>>   https://svn.apache.org/repos/asf/incubator/openjpa/branches/0.9.6-
>> incubating/
>>
>> I have tagged the sources at:
>>
>>   https://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-
>> incubating/
>>
>> 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:00PM EST on Thursday November
>> 23rd. A "+1" indicates that you approve of the release, a "-1"
>> indicates a vote against making a release.
>>
>> I'll get the ball rolling by adding my own vote: +1
>>
>>
>>
>>

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!


Re: Branch or tag?

Posted by "Geir Magnusson Jr." <ge...@pobox.com>.
Interesting - another approach that I've used when the trunk is kept in 
a releasable state, you can tag the trunk for a release, ex 1.1, and 
then if you need to keep working on that for bugfixes (1.1.1), you do a 
branch and keep going.

Many ways to skin this cat...

Kevin Sutter wrote:
> Good points, Craig.
> 
> Since there is always the possibility of maintaining a branch, we need a 
> tag
> to represent the beginning of that branch -- with no changes ever being
> committed to the tag.  And, since I don't want to be tied to some 
> particular
> naming convention (and I think it would be very confusing), I don't want to
> pre-create a branch.
> 
> Bottom line, there is a need and desire for both tags and branches.  And, I
> agree with Craig, that we don't create the tag until we are sure that a
> given branch is released.
> 
> Kevin
> 
> On 11/21/06, Craig L Russell <Cr...@sun.com> wrote:
>>
>> Hi Kevin,
>>
>> It's my understanding as well that there's no difference between a
>> branch and a tag from the svn perspective.
>>
>> I'd like to see the tag created only after we release, if at all. The
>> question for me is whether we would ever change the branch for 0.9.6
>> after we release it. If not, then I agree that there is no need for a
>> tag as well.
>>
>> But to take perhaps a more interesting sequence, let's say we release
>> OpenJPA 1.1. We create the 1.1 branch and release it, while changing
>> the trunk to be 1.2-SNAPSHOT. Now we have a bunch of bug fixes for
>> 1.1 and want to release a 1.1.1. We have a choice between a) doing
>> the bug fixing on the 1.1 branch itself and creating the 1.1.1 branch
>> when we want to release 1.1.1; OR b) create the 1.1.1 branch
>> immediately after releasing the 1.1 branch.
>>
>> With a, we need to tag the 1.1 branch before applying any bug fixes.
>> With b, we don't need to tag but have to remember that any bug fixes
>> should be applied to 1.1.1 branch instead of the 1.1 branch.
>>
>> Craig
>>
>> On Nov 21, 2006, at 8:16 AM, Kevin Sutter wrote:
>>
>> > Marc,
>> > +1 for the 0.9.6 release
>> >
>> > Question though...  Since tags and branches are virtually the same
>> > thing in
>> > SVN, do we really need to have both the tagged version and the
>> > branch?  It
>> > seems that the branch would be sufficient and then just remove the
>> > tags
>> > folder altogether.  Unless I am missing some aspect of the tag that
>> > you are
>> > taking advantage of...
>> >
>> > Kevin
>> >
>> >
>> > On 11/20/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
>> >>
>> >> OpenJPA People-
>> >>
>> >> In accordance with the Incubating Releases guidelines at  http://
>> >> incubator.apache.org/incubation/Incubation_Policy.html#Releases , I'd
>> >> like to take a third shot at making an OpenJPA release and start a
>> >> vote on publishing a "0.9.6-incubating" release of OpenJPA. The last
>> >> couple votes failed due to some problems with the notice file and
>> >> some source files that were missing license headers and other
>> >> miscellaneous issues.
>> >>
>> >> The release candidate is at:
>> >>
>> >> http://people.apache.org/repo/m2-incubating-repository/org/apache/
>> >> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
>> >> incubating-binary.zip
>> >>
>> >> The GPG signature and MD5 checksums are at:
>> >>
>> >>   http://people.apache.org/repo/m2-incubating-repository/org/apache/
>> >> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
>> >> incubating-binary.zip.asc
>> >>   http://people.apache.org/repo/m2-incubating-repository/org/apache/
>> >> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
>> >> incubating-binary.zip.md5
>> >>
>> >> The sources, sources GPG signature and sources MD5 checksum are
>> >> available at:
>> >>
>> >>   http://people.apache.org/repo/m2-incubating-repository/org/apache/
>> >> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
>> >> incubating-source.zip
>> >>   http://people.apache.org/repo/m2-incubating-repository/org/apache/
>> >> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
>> >> incubating-source.zip.asc
>> >>   http://people.apache.org/repo/m2-incubating-repository/org/apache/
>> >> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
>> >> incubating-source.zip.md5
>> >>
>> >> This build was cut from the branch at:
>> >>
>> >>   https://svn.apache.org/repos/asf/incubator/openjpa/branches/0.9.6-
>> >> incubating/
>> >>
>> >> I have tagged the sources at:
>> >>
>> >>   https://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-
>> >> incubating/
>> >>
>> >> 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:00PM EST on Thursday November
>> >> 23rd. A "+1" indicates that you approve of the release, a "-1"
>> >> indicates a vote against making a release.
>> >>
>> >> I'll get the ball rolling by adding my own vote: +1
>> >>
>> >>
>> >>
>> >>
>>
>> Craig Russell
>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>> 408 276-5638 mailto:Craig.Russell@sun.com
>> P.S. A good JDO? O, Gasp!
>>
>>
>>
>>
> 

Re: Branch or tag?

Posted by Craig L Russell <Cr...@Sun.COM>.
On Nov 21, 2006, at 12:09 PM, Patrick Linskey wrote:

>>>> Since there is always the possibility of maintaining a
>>>> branch, we need a tag
>>>> to represent the beginning of that branch -- with no changes
>>>> ever being
>>>> committed to the tag.
>>>
>>> Really? I was under the assumption that svn took care of remembering
>>> where the branch was moved from, thus getting rid of the
>> need for the
>>> extra branch and simplifying merging. But I could be wrong, as I've
>>> never merged in svn.
>>
>> All of these tags and branches are just a convenience for people so
>> they don't have to scour the svn commit log to figure out what bits
>> are where.
>>
>> So when you create a branch, you could always remember which svn
>> version that was and recreate the branch as it existed from the
>> version number when you branched. But once you change the branch, I
>> think what we really want to remember is the final version that was
>> released, so if we need to go back and say "now, what were those
>> released bits created from?" then we simply check out the tag and we
>> have the sources that were used for the release.
>
> My interpretation of what Kevin said was that we needed to know the  
> start
> point (tag or revision number) of the branch in order to do svn merge
> operations (i.e., to merge the branch changes back into the trunk).  
> That
> sounds a lot like what I've had to do when using CVS in the past; I  
> was
> under the impression that svn handled merging much better than did  
> CVS.
>
> Ignoring any differences between revision numbers and symbolic  
> tags, does
> anyone know if we need to know the branch origin in order to do a  
> merge
> successfully in svn?

Ah, that question is not in my area of expertise. I have assumed that  
svn is happy to try to merge anything into anything else. I've never  
done a wholesale merge, but have always merged individual files.

Craig
>
> -Patrick

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!


RE: Branch or tag?

Posted by Patrick Linskey <pl...@bea.com>.
> >> Since there is always the possibility of maintaining a
> >> branch, we need a tag
> >> to represent the beginning of that branch -- with no changes
> >> ever being
> >> committed to the tag.
> >
> > Really? I was under the assumption that svn took care of remembering
> > where the branch was moved from, thus getting rid of the 
> need for the
> > extra branch and simplifying merging. But I could be wrong, as I've
> > never merged in svn.
> 
> All of these tags and branches are just a convenience for people so  
> they don't have to scour the svn commit log to figure out what bits  
> are where.
> 
> So when you create a branch, you could always remember which svn  
> version that was and recreate the branch as it existed from the  
> version number when you branched. But once you change the branch, I  
> think what we really want to remember is the final version that was  
> released, so if we need to go back and say "now, what were those  
> released bits created from?" then we simply check out the tag and we  
> have the sources that were used for the release.

My interpretation of what Kevin said was that we needed to know the start
point (tag or revision number) of the branch in order to do svn merge
operations (i.e., to merge the branch changes back into the trunk). That
sounds a lot like what I've had to do when using CVS in the past; I was
under the impression that svn handled merging much better than did CVS.

Ignoring any differences between revision numbers and symbolic tags, does
anyone know if we need to know the branch origin in order to do a merge
successfully in svn?

-Patrick
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

Re: Branch or tag?

Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Patrick,

On Nov 21, 2006, at 11:17 AM, Patrick Linskey wrote:

>> Since there is always the possibility of maintaining a
>> branch, we need a tag
>> to represent the beginning of that branch -- with no changes
>> ever being
>> committed to the tag.
>
> Really? I was under the assumption that svn took care of remembering
> where the branch was moved from, thus getting rid of the need for the
> extra branch and simplifying merging. But I could be wrong, as I've
> never merged in svn.

All of these tags and branches are just a convenience for people so  
they don't have to scour the svn commit log to figure out what bits  
are where.

So when you create a branch, you could always remember which svn  
version that was and recreate the branch as it existed from the  
version number when you branched. But once you change the branch, I  
think what we really want to remember is the final version that was  
released, so if we need to go back and say "now, what were those  
released bits created from?" then we simply check out the tag and we  
have the sources that were used for the release.

Craig

>
> -Patrick
> ______________________________________________________________________ 
> _
> Notice:  This email message, together with any attachments, may  
> contain
> information  of  BEA Systems,  Inc.,  its subsidiaries  and   
> affiliated
> entities,  that may be confidential,  proprietary,  copyrighted   
> and/or
> legally privileged, and is intended solely for the use of the  
> individual
> or entity named in this message. If you are not the intended  
> recipient,
> and have received this message in error, please immediately return  
> this
> by email and then delete it.

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!


RE: Branch or tag?

Posted by Patrick Linskey <pl...@bea.com>.
> Since there is always the possibility of maintaining a 
> branch, we need a tag
> to represent the beginning of that branch -- with no changes 
> ever being
> committed to the tag.

Really? I was under the assumption that svn took care of remembering
where the branch was moved from, thus getting rid of the need for the
extra branch and simplifying merging. But I could be wrong, as I've
never merged in svn.

-Patrick
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

Re: Branch or tag?

Posted by Kevin Sutter <kw...@gmail.com>.
Good points, Craig.

Since there is always the possibility of maintaining a branch, we need a tag
to represent the beginning of that branch -- with no changes ever being
committed to the tag.  And, since I don't want to be tied to some particular
naming convention (and I think it would be very confusing), I don't want to
pre-create a branch.

Bottom line, there is a need and desire for both tags and branches.  And, I
agree with Craig, that we don't create the tag until we are sure that a
given branch is released.

Kevin

On 11/21/06, Craig L Russell <Cr...@sun.com> wrote:
>
> Hi Kevin,
>
> It's my understanding as well that there's no difference between a
> branch and a tag from the svn perspective.
>
> I'd like to see the tag created only after we release, if at all. The
> question for me is whether we would ever change the branch for 0.9.6
> after we release it. If not, then I agree that there is no need for a
> tag as well.
>
> But to take perhaps a more interesting sequence, let's say we release
> OpenJPA 1.1. We create the 1.1 branch and release it, while changing
> the trunk to be 1.2-SNAPSHOT. Now we have a bunch of bug fixes for
> 1.1 and want to release a 1.1.1. We have a choice between a) doing
> the bug fixing on the 1.1 branch itself and creating the 1.1.1 branch
> when we want to release 1.1.1; OR b) create the 1.1.1 branch
> immediately after releasing the 1.1 branch.
>
> With a, we need to tag the 1.1 branch before applying any bug fixes.
> With b, we don't need to tag but have to remember that any bug fixes
> should be applied to 1.1.1 branch instead of the 1.1 branch.
>
> Craig
>
> On Nov 21, 2006, at 8:16 AM, Kevin Sutter wrote:
>
> > Marc,
> > +1 for the 0.9.6 release
> >
> > Question though...  Since tags and branches are virtually the same
> > thing in
> > SVN, do we really need to have both the tagged version and the
> > branch?  It
> > seems that the branch would be sufficient and then just remove the
> > tags
> > folder altogether.  Unless I am missing some aspect of the tag that
> > you are
> > taking advantage of...
> >
> > Kevin
> >
> >
> > On 11/20/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
> >>
> >> OpenJPA People-
> >>
> >> In accordance with the Incubating Releases guidelines at  http://
> >> incubator.apache.org/incubation/Incubation_Policy.html#Releases , I'd
> >> like to take a third shot at making an OpenJPA release and start a
> >> vote on publishing a "0.9.6-incubating" release of OpenJPA. The last
> >> couple votes failed due to some problems with the notice file and
> >> some source files that were missing license headers and other
> >> miscellaneous issues.
> >>
> >> The release candidate is at:
> >>
> >> http://people.apache.org/repo/m2-incubating-repository/org/apache/
> >> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
> >> incubating-binary.zip
> >>
> >> The GPG signature and MD5 checksums are at:
> >>
> >>   http://people.apache.org/repo/m2-incubating-repository/org/apache/
> >> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
> >> incubating-binary.zip.asc
> >>   http://people.apache.org/repo/m2-incubating-repository/org/apache/
> >> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
> >> incubating-binary.zip.md5
> >>
> >> The sources, sources GPG signature and sources MD5 checksum are
> >> available at:
> >>
> >>   http://people.apache.org/repo/m2-incubating-repository/org/apache/
> >> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
> >> incubating-source.zip
> >>   http://people.apache.org/repo/m2-incubating-repository/org/apache/
> >> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
> >> incubating-source.zip.asc
> >>   http://people.apache.org/repo/m2-incubating-repository/org/apache/
> >> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
> >> incubating-source.zip.md5
> >>
> >> This build was cut from the branch at:
> >>
> >>   https://svn.apache.org/repos/asf/incubator/openjpa/branches/0.9.6-
> >> incubating/
> >>
> >> I have tagged the sources at:
> >>
> >>   https://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-
> >> incubating/
> >>
> >> 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:00PM EST on Thursday November
> >> 23rd. A "+1" indicates that you approve of the release, a "-1"
> >> indicates a vote against making a release.
> >>
> >> I'll get the ball rolling by adding my own vote: +1
> >>
> >>
> >>
> >>
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
>
>
>

RE: Branch or tag?

Posted by Patrick Linskey <pl...@bea.com>.
I was thinking about this a bunch yesterday, and came up with the following:

1. Moving forward, I think that we'll eventually start doing different
projects in different branches. In the past, for a project of this size,
I've seen a lot of success using a mainline approach, where the bulk of new
development happens on the mainline, and we make branches for hardening
before a release. So, sometime before 1.0 is released, we'd have a 1.0
branch, and non-1.0 related new projects would happen in the mainline.

2. Given the back-and-forth vote process (which will hopefully get
streamlined over time as we get everything in place and automate things), it
seems like we might want to build releases from yet another branch, to keep
unwanted work out of the branches. This might be a non-issue in the future,
though, if we're already doing #1 above. 

3. If we care about point 2, one option might be to create a new directory
(/releases or /branches/releases, for example) that we release from.
However, my gut instinct is that if we do #1, this won't be an issue.

-Patrick

-- 
Patrick Linskey
BEA Systems, Inc. 

_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it. 

> -----Original Message-----
> From: Craig.Russell@Sun.COM [mailto:Craig.Russell@Sun.COM] 
> Sent: Tuesday, November 21, 2006 9:55 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: Branch or tag?
> 
> Hi Kevin,
> 
> It's my understanding as well that there's no difference between a  
> branch and a tag from the svn perspective.
> 
> I'd like to see the tag created only after we release, if at 
> all. The  
> question for me is whether we would ever change the branch for 0.9.6  
> after we release it. If not, then I agree that there is no 
> need for a  
> tag as well.
> 
> But to take perhaps a more interesting sequence, let's say we 
> release  
> OpenJPA 1.1. We create the 1.1 branch and release it, while changing  
> the trunk to be 1.2-SNAPSHOT. Now we have a bunch of bug fixes for  
> 1.1 and want to release a 1.1.1. We have a choice between a) doing  
> the bug fixing on the 1.1 branch itself and creating the 
> 1.1.1 branch  
> when we want to release 1.1.1; OR b) create the 1.1.1 branch  
> immediately after releasing the 1.1 branch.
> 
> With a, we need to tag the 1.1 branch before applying any bug fixes.  
> With b, we don't need to tag but have to remember that any bug fixes  
> should be applied to 1.1.1 branch instead of the 1.1 branch.
> 
> Craig
> 
> On Nov 21, 2006, at 8:16 AM, Kevin Sutter wrote:
> 
> > Marc,
> > +1 for the 0.9.6 release
> >
> > Question though...  Since tags and branches are virtually the same  
> > thing in
> > SVN, do we really need to have both the tagged version and the  
> > branch?  It
> > seems that the branch would be sufficient and then just remove the  
> > tags
> > folder altogether.  Unless I am missing some aspect of the 
> tag that  
> > you are
> > taking advantage of...
> >
> > Kevin
> >
> >
> > On 11/20/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
> >>
> >> OpenJPA People-
> >>
> >> In accordance with the Incubating Releases guidelines at  http://
> >> 
> incubator.apache.org/incubation/Incubation_Policy.html#Releases , I'd
> >> like to take a third shot at making an OpenJPA release and start a
> >> vote on publishing a "0.9.6-incubating" release of 
> OpenJPA. The last
> >> couple votes failed due to some problems with the notice file and
> >> some source files that were missing license headers and other
> >> miscellaneous issues.
> >>
> >> The release candidate is at:
> >>
> >> http://people.apache.org/repo/m2-incubating-repository/org/apache/
> >> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
> >> incubating-binary.zip
> >>
> >> The GPG signature and MD5 checksums are at:
> >>
> >>   
> http://people.apache.org/repo/m2-incubating-repository/org/apache/
> >> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
> >> incubating-binary.zip.asc
> >>   
> http://people.apache.org/repo/m2-incubating-repository/org/apache/
> >> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
> >> incubating-binary.zip.md5
> >>
> >> The sources, sources GPG signature and sources MD5 checksum are
> >> available at:
> >>
> >>   
> http://people.apache.org/repo/m2-incubating-repository/org/apache/
> >> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
> >> incubating-source.zip
> >>   
> http://people.apache.org/repo/m2-incubating-repository/org/apache/
> >> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
> >> incubating-source.zip.asc
> >>   
> http://people.apache.org/repo/m2-incubating-repository/org/apache/
> >> openjpa/openjpa-project/0.9.6-incubating/openjpa-project-0.9.6-
> >> incubating-source.zip.md5
> >>
> >> This build was cut from the branch at:
> >>
> >>   
> https://svn.apache.org/repos/asf/incubator/openjpa/branches/0.9.6-
> >> incubating/
> >>
> >> I have tagged the sources at:
> >>
> >>   https://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-
> >> incubating/
> >>
> >> 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:00PM EST on Thursday November
> >> 23rd. A "+1" indicates that you approve of the release, a "-1"
> >> indicates a vote against making a release.
> >>
> >> I'll get the ball rolling by adding my own vote: +1
> >>
> >>
> >>
> >>
> 
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
> 
>