You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Marc Prud'hommeaux <mp...@apache.org> on 2006/11/16 01:19:33 UTC
[VOTE] publish openjpa 0.9.6-incubating release
The OpenJPA incubator community voted on and has approved a proposal
to release OpenJPA 0.9.6-incubating. Pursuant to the Releases section
of the Incubation Policy (http://incubator.apache.org/incubation/
Incubation_Policy.html#Releases ) we would now like to request the
permission of the Incubator PMC to publish the release zip file on
the openjpa download page (http://cwiki.apache.org/openjpa/
downloads.html).
Proposal:
http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-dev/
200611.mbox/%3cD51C3843-E71F-42C7-AA89-75949FF19D5D@apache.org%3e
Vote result:
http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-dev/
200611.mbox/%3c9A571E60-CA08-4386-9E2A-3AB31E26D3DC@apache.org%3e
We look forward to the vote passing and seeing an initial incubation
release of OpenJPA!
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OpenJPA IP clearance (was: Re: [VOTE] publish openjpa 0.9.6-incubating release)
Posted by robert burrell donkin <ro...@gmail.com>.
On 11/22/06, Eddie O'Neil <ek...@gmail.com> wrote:
> I can take care of the page once we've confirmed that the code was recorded.
>
> Geir, you've got more experience with this than I -- any idea where
> the OpenJPA code grant documented? I didn't find it in grants.txt.
sometimes corporate code comes in as a grant, sometimes as a ccla-with-grant
there's something which sounds about right in cclas.txt but someone
more familar with the contents needs to confirm...
- robert
Re: OpenJPA IP clearance (was: Re: [VOTE] publish openjpa 0.9.6-incubating release)
Posted by Eddie O'Neil <ek...@gmail.com>.
I can take care of the page once we've confirmed that the code was recorded.
Geir, you've got more experience with this than I -- any idea where
the OpenJPA code grant documented? I didn't find it in grants.txt.
Eddie
ps -- to update the Incubator website, you need two things:
#1: Check this out of SVN:
http://svn.apache.org/repos/asf/incubator/public/trunk/
#2: Karma to commit changes and then sync those changes onto
/www/incubator.apache.org/projects
I think Geir made it this easy a while ago -- nice work. :)
On 11/22/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
> OpenJPA People-
>
> Does anyone have any insight into Eddie's question below (which is in
> response to point #1 of the objection to the most recent OpenJPA
> release vote, which can be seen at http://mail-archives.apache.org/
> mod_mbox/incubator-general/200611.mbox/%
> 3cf470f68e0611161257h2ff87409qdf5250fb1831e51b@mail.gmail.com%3e )?
>
> Also, if it is just a matter of updating the http://
> incubator.apache.org/projects/openjpa.html page, does anyone know how
> to go about doing that? AFAIK, since it is not under our project's
> directory of http://incubator.apache.org/openjpa/ , we can't edit it
> the same way we can edit our own site.
>
> I believe this is the last showstopper for getting through the vote
> on general@incubator.apache.org (assuming the current vote on open-
> jpa-dev@incubator.apache.org passes).
>
>
>
> On Nov 16, 2006, at 6:20 PM, Eddie O'Neil wrote:
>
> > On Robert's point about IP clearance, I'd marked that as TODO
> > because I didn't see an obvious place where the code grant for OpenJPA
> > had been recorded from BEA.
> >
> > Geir, do you know where this might be? I did check grants.txt but
> > might have missed it.
> >
> > Thanks.
> >
> > Eddie
> >
> >
> > On 11/16/06, Craig L Russell <Cr...@sun.com> wrote:
> >> Hi Robert,
> >>
> >> On Nov 16, 2006, at 12:14 PM, robert burrell donkin wrote:
> >>
> >> > On 11/16/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
> >> >>
> >> >> The OpenJPA incubator community voted on and has approved a
> >> proposal
> >> >> to release OpenJPA 0.9.6-incubating. Pursuant to the Releases
> >> section
> >> >> of the Incubation Policy (http://incubator.apache.org/incubation/
> >> >> Incubation_Policy.html#Releases ) we would now like to request the
> >> >> permission of the Incubator PMC to publish the release zip file on
> >> >> the openjpa download page (http://cwiki.apache.org/openjpa/
> >> >> downloads.html).
> >> >>
> >> >>
> >> >> Proposal:
> >> >>
> >> >> http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-
> >> dev/
> >> >> 200611.mbox/%3cD51C3843-E71F-42C7-AA89-75949FF19D5D@apache.org%3e
> >> >>
> >> >> Vote result:
> >> >>
> >> >> http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-
> >> dev/
> >> >> 200611.mbox/%3c9A571E60-CA08-4386-9E2A-3AB31E26D3DC@apache.org%3e
> >> >
> >> > what's the url for the artifacts to be released?
> >>
> >> The artifacts are staged 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
> >>
> >> Is this what you meant?
> >>
> >> Craig
> >> >
> >> > - robert
> >> >
> >> >
> >> ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> > For additional commands, e-mail: general-help@incubator.apache.org
> >> >
> >>
> >> 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!
> >>
> >>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
>
OpenJPA IP clearance (was: Re: [VOTE] publish openjpa 0.9.6-incubating release)
Posted by Marc Prud'hommeaux <mp...@apache.org>.
OpenJPA People-
Does anyone have any insight into Eddie's question below (which is in
response to point #1 of the objection to the most recent OpenJPA
release vote, which can be seen at http://mail-archives.apache.org/
mod_mbox/incubator-general/200611.mbox/%
3cf470f68e0611161257h2ff87409qdf5250fb1831e51b@mail.gmail.com%3e )?
Also, if it is just a matter of updating the http://
incubator.apache.org/projects/openjpa.html page, does anyone know how
to go about doing that? AFAIK, since it is not under our project's
directory of http://incubator.apache.org/openjpa/ , we can't edit it
the same way we can edit our own site.
I believe this is the last showstopper for getting through the vote
on general@incubator.apache.org (assuming the current vote on open-
jpa-dev@incubator.apache.org passes).
On Nov 16, 2006, at 6:20 PM, Eddie O'Neil wrote:
> On Robert's point about IP clearance, I'd marked that as TODO
> because I didn't see an obvious place where the code grant for OpenJPA
> had been recorded from BEA.
>
> Geir, do you know where this might be? I did check grants.txt but
> might have missed it.
>
> Thanks.
>
> Eddie
>
>
> On 11/16/06, Craig L Russell <Cr...@sun.com> wrote:
>> Hi Robert,
>>
>> On Nov 16, 2006, at 12:14 PM, robert burrell donkin wrote:
>>
>> > On 11/16/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
>> >>
>> >> The OpenJPA incubator community voted on and has approved a
>> proposal
>> >> to release OpenJPA 0.9.6-incubating. Pursuant to the Releases
>> section
>> >> of the Incubation Policy (http://incubator.apache.org/incubation/
>> >> Incubation_Policy.html#Releases ) we would now like to request the
>> >> permission of the Incubator PMC to publish the release zip file on
>> >> the openjpa download page (http://cwiki.apache.org/openjpa/
>> >> downloads.html).
>> >>
>> >>
>> >> Proposal:
>> >>
>> >> http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-
>> dev/
>> >> 200611.mbox/%3cD51C3843-E71F-42C7-AA89-75949FF19D5D@apache.org%3e
>> >>
>> >> Vote result:
>> >>
>> >> http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-
>> dev/
>> >> 200611.mbox/%3c9A571E60-CA08-4386-9E2A-3AB31E26D3DC@apache.org%3e
>> >
>> > what's the url for the artifacts to be released?
>>
>> The artifacts are staged 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
>>
>> Is this what you meant?
>>
>> Craig
>> >
>> > - robert
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> > For additional commands, e-mail: general-help@incubator.apache.org
>> >
>>
>> 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!
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by Eddie O'Neil <ek...@gmail.com>.
On Robert's point about IP clearance, I'd marked that as TODO
because I didn't see an obvious place where the code grant for OpenJPA
had been recorded from BEA.
Geir, do you know where this might be? I did check grants.txt but
might have missed it.
Thanks.
Eddie
On 11/16/06, Craig L Russell <Cr...@sun.com> wrote:
> Hi Robert,
>
> On Nov 16, 2006, at 12:14 PM, robert burrell donkin wrote:
>
> > On 11/16/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
> >>
> >> The OpenJPA incubator community voted on and has approved a proposal
> >> to release OpenJPA 0.9.6-incubating. Pursuant to the Releases section
> >> of the Incubation Policy (http://incubator.apache.org/incubation/
> >> Incubation_Policy.html#Releases ) we would now like to request the
> >> permission of the Incubator PMC to publish the release zip file on
> >> the openjpa download page (http://cwiki.apache.org/openjpa/
> >> downloads.html).
> >>
> >>
> >> Proposal:
> >>
> >> http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-dev/
> >> 200611.mbox/%3cD51C3843-E71F-42C7-AA89-75949FF19D5D@apache.org%3e
> >>
> >> Vote result:
> >>
> >> http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-dev/
> >> 200611.mbox/%3c9A571E60-CA08-4386-9E2A-3AB31E26D3DC@apache.org%3e
> >
> > what's the url for the artifacts to be released?
>
> The artifacts are staged 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
>
> Is this what you meant?
>
> Craig
> >
> > - robert
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
> 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!
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Robert,
On Nov 16, 2006, at 12:14 PM, robert burrell donkin wrote:
> On 11/16/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
>>
>> The OpenJPA incubator community voted on and has approved a proposal
>> to release OpenJPA 0.9.6-incubating. Pursuant to the Releases section
>> of the Incubation Policy (http://incubator.apache.org/incubation/
>> Incubation_Policy.html#Releases ) we would now like to request the
>> permission of the Incubator PMC to publish the release zip file on
>> the openjpa download page (http://cwiki.apache.org/openjpa/
>> downloads.html).
>>
>>
>> Proposal:
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-dev/
>> 200611.mbox/%3cD51C3843-E71F-42C7-AA89-75949FF19D5D@apache.org%3e
>>
>> Vote result:
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-dev/
>> 200611.mbox/%3c9A571E60-CA08-4386-9E2A-3AB31E26D3DC@apache.org%3e
>
> what's the url for the artifacts to be released?
The artifacts are staged 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
Is this what you meant?
Craig
>
> - robert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
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: [VOTE] publish openjpa 0.9.6-incubating release
Posted by robert burrell donkin <ro...@gmail.com>.
On 11/16/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
>
> > what's the url for the artifacts to be released?
>
> As mentioned in the vote proposal,
true
but this is a binding VOTE thread so it's good to have the information
noted here also for the record
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by Marc Prud'hommeaux <mp...@apache.org>.
> what's the url for the artifacts to be released?
As mentioned in the vote proposal, 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
On Nov 16, 2006, at 12:14 PM, robert burrell donkin wrote:
> On 11/16/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
>>
>> The OpenJPA incubator community voted on and has approved a proposal
>> to release OpenJPA 0.9.6-incubating. Pursuant to the Releases section
>> of the Incubation Policy (http://incubator.apache.org/incubation/
>> Incubation_Policy.html#Releases ) we would now like to request the
>> permission of the Incubator PMC to publish the release zip file on
>> the openjpa download page (http://cwiki.apache.org/openjpa/
>> downloads.html).
>>
>>
>> Proposal:
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-dev/
>> 200611.mbox/%3cD51C3843-E71F-42C7-AA89-75949FF19D5D@apache.org%3e
>>
>> Vote result:
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-dev/
>> 200611.mbox/%3c9A571E60-CA08-4386-9E2A-3AB31E26D3DC@apache.org%3e
>
> what's the url for the artifacts to be released?
>
> - robert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by robert burrell donkin <ro...@gmail.com>.
On 11/16/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
>
> The OpenJPA incubator community voted on and has approved a proposal
> to release OpenJPA 0.9.6-incubating. Pursuant to the Releases section
> of the Incubation Policy (http://incubator.apache.org/incubation/
> Incubation_Policy.html#Releases ) we would now like to request the
> permission of the Incubator PMC to publish the release zip file on
> the openjpa download page (http://cwiki.apache.org/openjpa/
> downloads.html).
>
>
> Proposal:
>
> http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-dev/
> 200611.mbox/%3cD51C3843-E71F-42C7-AA89-75949FF19D5D@apache.org%3e
>
> Vote result:
>
> http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-dev/
> 200611.mbox/%3c9A571E60-CA08-4386-9E2A-3AB31E26D3DC@apache.org%3e
what's the url for the artifacts to be released?
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by Kevin Sutter <kw...@gmail.com>.
+1
On 11/16/06, Patrick Linskey <pl...@bea.com> wrote:
>
> +1
>
> --
> 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: Geir Magnusson Jr. [mailto:geir@pobox.com]
> > Sent: Thursday, November 16, 2006 9:53 AM
> > To: general@incubator.apache.org
> > Subject: Re: [VOTE] publish openjpa 0.9.6-incubating release
> >
> > +1
> >
> > Marc Prud'hommeaux wrote:
> > >
> > > The OpenJPA incubator community voted on and has approved a
> > proposal to
> > > release OpenJPA 0.9.6-incubating. Pursuant to the Releases
> > section of
> > > the Incubation Policy
> > >
> > (http://incubator.apache.org/incubation/Incubation_Policy.html
> > #Releases
> > > ) we would now like to request the permission of the
> > Incubator PMC to
> > > publish the release zip file on the openjpa download page
> > > (http://cwiki.apache.org/openjpa/downloads.html).
> > >
> > >
> > > Proposal:
> > >
> > >
> > >
> > http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-de
> v/200611.mbox/%3cD51C3843-E71F-42C7-AA89-75949FF19D5D@apache.org%3e
> > >
> > >
> > > Vote result:
> > >
> > >
> > >
> > http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-de
> v/200611.mbox/%3c9A571E60-CA08-4386-9E2A-3AB31E26D3DC@apache.org%3e
> > >
> > >
> > > We look forward to the vote passing and seeing an initial
> > incubation
> > > release of OpenJPA!
> > >
> > >
> > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
RE: [VOTE] publish openjpa 0.9.6-incubating release
Posted by Patrick Linskey <pl...@bea.com>.
+1
--
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: Geir Magnusson Jr. [mailto:geir@pobox.com]
> Sent: Thursday, November 16, 2006 9:53 AM
> To: general@incubator.apache.org
> Subject: Re: [VOTE] publish openjpa 0.9.6-incubating release
>
> +1
>
> Marc Prud'hommeaux wrote:
> >
> > The OpenJPA incubator community voted on and has approved a
> proposal to
> > release OpenJPA 0.9.6-incubating. Pursuant to the Releases
> section of
> > the Incubation Policy
> >
> (http://incubator.apache.org/incubation/Incubation_Policy.html
> #Releases
> > ) we would now like to request the permission of the
> Incubator PMC to
> > publish the release zip file on the openjpa download page
> > (http://cwiki.apache.org/openjpa/downloads.html).
> >
> >
> > Proposal:
> >
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-de
v/200611.mbox/%3cD51C3843-E71F-42C7-AA89-75949FF19D5D@apache.org%3e
> >
> >
> > Vote result:
> >
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-de
v/200611.mbox/%3c9A571E60-CA08-4386-9E2A-3AB31E26D3DC@apache.org%3e
> >
> >
> > We look forward to the vote passing and seeing an initial
> incubation
> > release of OpenJPA!
> >
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by "Geir Magnusson Jr." <ge...@pobox.com>.
+1
Marc Prud'hommeaux wrote:
>
> The OpenJPA incubator community voted on and has approved a proposal to
> release OpenJPA 0.9.6-incubating. Pursuant to the Releases section of
> the Incubation Policy
> (http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
> ) we would now like to request the permission of the Incubator PMC to
> publish the release zip file on the openjpa download page
> (http://cwiki.apache.org/openjpa/downloads.html).
>
>
> Proposal:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-dev/200611.mbox/%3cD51C3843-E71F-42C7-AA89-75949FF19D5D@apache.org%3e
>
>
> Vote result:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-dev/200611.mbox/%3c9A571E60-CA08-4386-9E2A-3AB31E26D3DC@apache.org%3e
>
>
> We look forward to the vote passing and seeing an initial incubation
> release of OpenJPA!
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by Craig L Russell <Cr...@Sun.COM>.
Some of the smarter browsers will look at the .jar suffix and try to
execute it by looking at the manifest to find the Main program. This
is not the behavior we want. I don't know of any such issues
with .zip files. If these are automatically processed by the browser
download program, they typically simply decompress the file into a
directory, which is actually what is intended.
Craig
On Nov 16, 2006, at 6:22 PM, Marc Prud'hommeaux wrote:
> Roy-
>
> I think people use the ".zip" extensions because that is what most
> desktop managers will map to the decompression application. Also,
> recent version of Windows allow exploring of .zip file from within
> explorer.exe as if they were directory structures.
>
> To my knowledge, no OS is smart enough to be able to distinguish
> between a .jar that is just an archive of files vs. an
> executable .jar file (where double-clicking indicates that the
> jar's application should be launched).
>
> Of course, the existing .zip assembly file can always be unpacked
> using the "jar xvf ...zip" command, so no additional software
> should ever be required to unpack them.
>
>
> On Nov 16, 2006, at 5:49 PM, Roy T. Fielding wrote:
>
>> On Nov 16, 2006, at 5:22 PM, Marc Prud'hommeaux wrote:
>>>> BTW, why distribute a zip package? Wouldn't it be more sensible to
>>>> distribute as a jar? Just curious.
>>>
>>> The zip contains documentation, examples, and the dependency jars
>>> required to run the examples.
>>
>> Yes, I know that -- the point was that the jar format, as in
>>
>> jar cvf mypackage.jar mypackage
>>
>> is a general archive format that uses ZIP compression and can be
>> unpacked by anyone who has installed java. Is there a reason to
>> use a separate packaging format that is specific to winzip?
>>
>> I use gzipped tar for C releases and jar for java releases, but
>> I have also seen a lot of other java projects that distribute both
>> a .zip package and a tar.gz package. I was wondering if you knew
>> why.
>>
>> ....Roy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
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: [VOTE] publish openjpa 0.9.6-incubating release
Posted by Marc Prud'hommeaux <mp...@apache.org>.
Roy-
I think people use the ".zip" extensions because that is what most
desktop managers will map to the decompression application. Also,
recent version of Windows allow exploring of .zip file from within
explorer.exe as if they were directory structures.
To my knowledge, no OS is smart enough to be able to distinguish
between a .jar that is just an archive of files vs. an
executable .jar file (where double-clicking indicates that the jar's
application should be launched).
Of course, the existing .zip assembly file can always be unpacked
using the "jar xvf ...zip" command, so no additional software should
ever be required to unpack them.
On Nov 16, 2006, at 5:49 PM, Roy T. Fielding wrote:
> On Nov 16, 2006, at 5:22 PM, Marc Prud'hommeaux wrote:
>>> BTW, why distribute a zip package? Wouldn't it be more sensible to
>>> distribute as a jar? Just curious.
>>
>> The zip contains documentation, examples, and the dependency jars
>> required to run the examples.
>
> Yes, I know that -- the point was that the jar format, as in
>
> jar cvf mypackage.jar mypackage
>
> is a general archive format that uses ZIP compression and can be
> unpacked by anyone who has installed java. Is there a reason to
> use a separate packaging format that is specific to winzip?
>
> I use gzipped tar for C releases and jar for java releases, but
> I have also seen a lot of other java projects that distribute both
> a .zip package and a tar.gz package. I was wondering if you knew why.
>
> ....Roy
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by "Roy T. Fielding" <fi...@gbiv.com>.
On Nov 16, 2006, at 5:22 PM, Marc Prud'hommeaux wrote:
>> BTW, why distribute a zip package? Wouldn't it be more sensible to
>> distribute as a jar? Just curious.
>
> The zip contains documentation, examples, and the dependency jars
> required to run the examples.
Yes, I know that -- the point was that the jar format, as in
jar cvf mypackage.jar mypackage
is a general archive format that uses ZIP compression and can be
unpacked by anyone who has installed java. Is there a reason to
use a separate packaging format that is specific to winzip?
I use gzipped tar for C releases and jar for java releases, but
I have also seen a lot of other java projects that distribute both
a .zip package and a tar.gz package. I was wondering if you knew why.
....Roy
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by Marc Prud'hommeaux <mp...@apache.org>.
Roy-
On Nov 16, 2006, at 5:09 PM, Roy T. Fielding wrote:
> On Nov 16, 2006, at 4:30 PM, Marc Prud'hommeaux wrote:
>
>> We'll correct these issues asap. Once corrected artifacts are
>> uploaded, I assume it will necessary to re-start the vote on the
>> open-jpa-dev list before re-starting the vote here. Please correct
>> me if I am wrong.
>
> That is correct -- each release vote is on a specific sequence of
> bits.
> Also, be sure the other developers know what is being changed and why,
> so that the project as a whole learns how to make releases (and what
> they should be looking for before casting +1 votes).
Will do.
> BTW, why distribute a zip package? Wouldn't it be more sensible to
> distribute as a jar? Just curious.
The zip contains documentation, examples, and the dependency jars
required to run the examples.
> ....Roy
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by "Roy T. Fielding" <fi...@gbiv.com>.
On Nov 16, 2006, at 4:30 PM, Marc Prud'hommeaux wrote:
> We'll correct these issues asap. Once corrected artifacts are
> uploaded, I assume it will necessary to re-start the vote on the
> open-jpa-dev list before re-starting the vote here. Please correct
> me if I am wrong.
That is correct -- each release vote is on a specific sequence of bits.
Also, be sure the other developers know what is being changed and why,
so that the project as a whole learns how to make releases (and what
they should be looking for before casting +1 votes).
BTW, why distribute a zip package? Wouldn't it be more sensible to
distribute as a jar? Just curious.
....Roy
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by Kevan Miller <ke...@gmail.com>.
On Nov 30, 2006, at 1:19 PM, Marc Prud'hommeaux wrote:
> Kevan-
>
> Would you be amenable to having a single NOTICE file, but changing
> the wording to:
>
> "The OpenJPA binary zip distribution is bundled with the..."
>
> ?
Hi Marc,
Well, actually on closer reading of your LICENSE file, it looks like
two files in openjpa-all are CDDL licensed. So, I wouldn't recommend
that change. Please let me know if I'm incorrect...
In general, yes, that type of change would help. However, it still
requires some work on the embedder's part. I'd really prefer more
precision rather than conditional statements requiring some
analysis... That's my 2 cents, anyway...
--kevan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by Marc Prud'hommeaux <mp...@apache.org>.
Kevan-
Would you be amenable to having a single NOTICE file, but changing
the wording to:
"The OpenJPA binary zip distribution is bundled with the..."
?
On Nov 30, 2006, at 8:43 AM, Kevan Miller wrote:
>
> On Nov 18, 2006, at 9:49 AM, robert burrell donkin wrote:
>
>> On 11/17/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
>>> On Nov 16, 2006, at 12:57 PM, robert burrell donkin wrote:
>
> <snip>
>
>>> > -- questions --
>>> >
>>> > i can't find LICENSE, NOTICE or DISCLAIMER in
>>> > openjpa-all-0.9.6-incubating.jar. did you intend to prevent
>>> official
>>> > distribution through maven repositories?
>>>
>>> Oops ... we missed putting these in. I've corrected this for the
>>> LICENSE.txt and NOTICE.txt files. However, looking at http://
>>> www.apache.org/legal/src-headers.html#faq-binaries , I don't see any
>>> mention of including the DISCLAIMER file ... is there somewhere else
>>> that mentions that that file should be included in jars (or other
>>> binary artifacts)?
>>
>> you won't find it since this is not a general requirement for apache
>> releases :-)
>>
>> the IPMC requires a disclaimer text is distributed with each
>> artifact.
>> i guessed that since openjpa uses a DISCLAIMER.txt that it would make
>> sense to include this. feel free to shoot me down if you already
>> include the disclaimer in some other form.
>
> Marc,
> Apologies for jumping in so late.
>
> One request for the LICENSE/NOTICE files that you're adding to the
> openjpa-all jar file. Rather than including your global LICENSE/
> NOTICE files (that contain license/notice information for all
> artifacts in your binary release), could you limit the license/
> notice information only to the artifacts that are contained with in
> the openjpa-all archive? This allows embedding products to be more
> precise in their license/notice handling.
>
> For instance, your NOTICE file contains the following:
>
> * OpenJPA is bundled with the binaries from the JPA specification, by
> Sun Microsystems and licensed under the CDDL 1.0. The source
> code is
> available at: https://glassfish.dev.java.net/source/browse/
> glassfish/
>
> However, this does not apply (I believe) to the artifacts contained
> within openjpa-all. So, users of open-jpa may not have this
> dependency. Geonimo is embedding openjpa-all, but does not have a
> dependency on the Sun JPA specification (we have our own jpa spec
> API implementation).
>
> --kevan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by Kevan Miller <ke...@gmail.com>.
On Nov 18, 2006, at 9:49 AM, robert burrell donkin wrote:
> On 11/17/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
>> On Nov 16, 2006, at 12:57 PM, robert burrell donkin wrote:
<snip>
>> > -- questions --
>> >
>> > i can't find LICENSE, NOTICE or DISCLAIMER in
>> > openjpa-all-0.9.6-incubating.jar. did you intend to prevent
>> official
>> > distribution through maven repositories?
>>
>> Oops ... we missed putting these in. I've corrected this for the
>> LICENSE.txt and NOTICE.txt files. However, looking at http://
>> www.apache.org/legal/src-headers.html#faq-binaries , I don't see any
>> mention of including the DISCLAIMER file ... is there somewhere else
>> that mentions that that file should be included in jars (or other
>> binary artifacts)?
>
> you won't find it since this is not a general requirement for apache
> releases :-)
>
> the IPMC requires a disclaimer text is distributed with each artifact.
> i guessed that since openjpa uses a DISCLAIMER.txt that it would make
> sense to include this. feel free to shoot me down if you already
> include the disclaimer in some other form.
Marc,
Apologies for jumping in so late.
One request for the LICENSE/NOTICE files that you're adding to the
openjpa-all jar file. Rather than including your global LICENSE/
NOTICE files (that contain license/notice information for all
artifacts in your binary release), could you limit the license/notice
information only to the artifacts that are contained with in the
openjpa-all archive? This allows embedding products to be more
precise in their license/notice handling.
For instance, your NOTICE file contains the following:
* OpenJPA is bundled with the binaries from the JPA specification, by
Sun Microsystems and licensed under the CDDL 1.0. The source
code is
available at: https://glassfish.dev.java.net/source/browse/
glassfish/
However, this does not apply (I believe) to the artifacts contained
within openjpa-all. So, users of open-jpa may not have this
dependency. Geonimo is embedding openjpa-all, but does not have a
dependency on the Sun JPA specification (we have our own jpa spec API
implementation).
--kevan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by robert burrell donkin <ro...@gmail.com>.
On 11/18/06, Craig L Russell <Cr...@sun.com> wrote:
> Hi Robert,
>
> I just have to give you a very public THANK YOU for your assistance
> to projects in the incubator. I personally look forward to reading
> your posts because I learn so much from them. I think you are a model
> for how to give constructive feedback and nurture projects. Please
> keep up the terrific work.
(being an englishman of the self-deprecating sort, public praise makes
me unconfortable :-/ but thanks anyway...)
but if there's any credit due, it's to those that taught me how to cut
releases (i won't embarrass them by naming names since most are still
around) by a similar process, and to the infrastructure and legal
teams who actually did the hard thinking (rather than the easier
talking)
respect (you know who you are)
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Robert,
I just have to give you a very public THANK YOU for your assistance
to projects in the incubator. I personally look forward to reading
your posts because I learn so much from them. I think you are a model
for how to give constructive feedback and nurture projects. Please
keep up the terrific work.
Thanks,
Craig
On Nov 18, 2006, at 6:49 AM, robert burrell donkin wrote:
> On 11/17/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
>> On Nov 16, 2006, at 12:57 PM, robert burrell donkin wrote:
>> > On 11/16/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
>
> <snip>
>
>> > i have some issues i'd like to see fixed plus less important
>> issues,
>> > some questions i'd like answered and some comments just FYI
>> >
>> > -- issues (i would like to see fixed) --
>
> <snip>
>
>> > openjpa distributes some jars in the binary. NOTICE.txt is ok (but
>> > note http://www.apache.org/legal/src-headers.html now asks that
>> apache
>> > collective copyright is included) but their licenses are not
>> included
>> > in LICENSE.txt. see
>> > http://incubator.apache.org/guides/examples/LICENSE for example.
>>
>> The only two non-ASF jars in the distribution are serp-1.11.0.jar
>> (BSD license) and persistence-api-1.0.jar (Sun CDDL). I've added
>> their licenses into our LICENSE.txt. I'd appreciate if you could take
>> a glance at the text (at https://svn.apache.org/repos/asf/incubator/
>> openjpa/trunk/openjpa-project/LICENSE.txt ) and let me know if that
>> looks sufficient.
>
> looks good :-)
>
>> Also, I don't think I need to add the licenses for the ASF jars that
>> are included with the binaries. If I'm incorrect about that, please
>> let me know, and I'll paste in the text of their identical licenses
>> to our LICENSE.txt file.
>
> no need to add duplicate copies of each particular LICENSE
>
> the aim is to inform downstream users in particular packages about the
> LICENSE for each artifact distributed. this is good for both legal and
> social reasons. it's up to the project how they achieve this goal.
> there are other acceptable ways used but the example is a commonly
> used approach.
>
>> > source distribution is missing LICENSE, NOTICE and DISCLAIMER at
>> the
>> > top level. (these probably need to be commit into svn.)
>>
>> As an exact snapshot of the buildable sources, these files were
>> included in the "openjpa-project" sub-directory of the sources
>> package. Reviewing http://www.apache.org/legal/src-
>> headers.html#notice , I see that they need to be included in the top
>> directory of any artifact, so I've added a directive to the source
>> distribution build to add them there.
>
> (i personally distrust source distribution processing of any kind. i
> worry about reproducability. but this is a matter for the project so)
> that should be ok
>
>> > -- minor issues --
>> >
>> > http://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-
>> > incubating/src/site/apt/*.apt
>> > lack license headers. apt supports comments so these should
>> probably
>> > have headers.
>>
>> I've added license headers to these files. I hadn't realized that apt
>> supported comments.
>
> seems to be an under-advertised feature :-)
>
>> > -- questions --
>> >
>> > i can't find LICENSE, NOTICE or DISCLAIMER in
>> > openjpa-all-0.9.6-incubating.jar. did you intend to prevent
>> official
>> > distribution through maven repositories?
>>
>> Oops ... we missed putting these in. I've corrected this for the
>> LICENSE.txt and NOTICE.txt files. However, looking at http://
>> www.apache.org/legal/src-headers.html#faq-binaries , I don't see any
>> mention of including the DISCLAIMER file ... is there somewhere else
>> that mentions that that file should be included in jars (or other
>> binary artifacts)?
>
> you won't find it since this is not a general requirement for apache
> releases :-)
>
> the IPMC requires a disclaimer text is distributed with each artifact.
> i guessed that since openjpa uses a DISCLAIMER.txt that it would make
> sense to include this. feel free to shoot me down if you already
> include the disclaimer in some other form.
>
>> > (RAT)
>> >
>> > http://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-
>> > incubating/openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/
>> > schema/schemas-doctype.rsrc
>> > has no license header. is this a generated file?
>>
>> No, but I don't think the format supports comments.
>
> i'm going to assume that it's a DTD
>
> AIUI it's possible to include xml style comments (<!-- -->) in all
> parsed entities (those that start with a prolog for example <?xml
> version='1.0'?>) but i'm willing to stand corrected...
>
> this isn't a release stopper for me
>
>> > http://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-
>> > incubating/openjpa-persistence/src/main/resources/org/apache/
>> > openjpa/persistence/orm-xsd.rsrc
>> > has no license header. is this a generated file?
>>
>> I'm not sure what to do about that one ... it is a cached copy of
>> http://java.sun.com/xml/ns/persistence/orm_1_0.xsd which we use for
>> XML schema validation without having to go to the web (which would be
>> prohibitive). The original schema doesn't specify any license, and
>> I'm not sure what the implicit license would be, but I also wouldn't
>> feel right about sticking in an Apache license header for a file that
>> we obviously didn't create.
>
> exactly right: never just stick headers in anything without clear
> provinence
>
>> Any thoughts?
>
> in the absence of any clear license, there is a link at the bottom of
> http://java.sun.com/xml/ns/persistence/ which says
> http://developers.sun.com/license/berkeley_license.html. arguable,
> though, it's part of the RI which is probably LGPL'd.
>
> but all this seems far too flimsy for comfort
>
> i recommend taking this up on legal-discuss and (if possible)
> contacting sun directly for clear guidance about their intended
> license. it would be cleaner and clearer if they embedded the license
> in the document or (at least) included the information in
> http://java.sun.com/xml/ns/persistence.
>
> unfortunately, this sounds like it might take a while to sort out :-/
>
> might be quicker just to create a clean room implementation direct
> from the specification
>
>> > -- comments --
>> >
>> > --- notes and suggestions (for future reference) ---
>> >
>> > there is no need to create sums for detached signatures.
>>
>> Maven seems to automatically attach .md5 and .sha1 checksums to all
>> uploaded artifacts. Since we are generating the .asc signatures in
>> the Maven process, it seems to include these in the list of artifacts
>> to sign. There doesn't seem to be any way to disable this, and the
>> convenience gained by having these files generated and uploaded as
>> part of the Maven build process outweighed the annoyance of having
>> these vestigial checksums lying around (IMO).
>
> fine
>
>> > some users (typically on *nix) prefer either bz2'd or tar.gz's
>> > distributions. creating additional artifacts is quick and easy
>> so this
>> > is an easy way to make life just a little easier for some users.
>>
>> We briefly discussed this on the open-jpa-list. While it is certainly
>> de-facto convention to release under both .zip and .tar.gz packaging
>> types, the only compelling reason to do so appears to be that UNIX
>> executable permissions are lost in the zip format. Since we don't
>> have any executables in the openjpa distribution, there doesn't seem
>> to be much reason to have additional packaging formats.
>>
>> We'd be interested in knowing if there are other advantages to having
>> multiple packaging mechanisms, though.
>
> releases are important guerrilla advertising for a project :-)
>
> user expectation and convenience. users expect projects that produce
> just zip'd distributions to be windows centric. distributions with
> alternative compression are easy and quick to produce. so IMHO it
> makes sense to distribute .tar.gz'd as well as zip'd just to make
> *nix'ers feel at home. good for linux-centric grassroots news channels
> (such as freshmeat) as well.
>
> but it's for the community to decide so it's the debate that's
> important
>
> <snip>
>
>> > there is no RELEASE_NOTES in the base directory. for open source
>> > projects, these serve as an important communication to users. the
>> > content will often serve for reuse in announcements and other
>> > grassroots publicity. consider creating them for the next release.
>>
>> We don't have one since this is our initial release, so the whole
>> package is effectively one big release note :)
>
> RELEASE_NOTES are important guerrilla advertising for a project :-)
>
> the content is often reused for announcements and for grassroots news
> channels such as freshmeat. release notes should describe a project's
> purpose and aims, how people can get involved, list sources of
> information and give some general information about the project's
> plans.
>
> - robert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
Craig Russell
clr@apache.org http://db.apache.org/jdo
Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by Endre Stølsvik <Ap...@Stolsvik.com>.
James Strachan wrote:
> On 11/21/06, Patrick Linskey <pl...@bea.com> wrote:
>> What do you do when it comes time to vote? Clearly, you can't be voting
>> on the RC build, as that's not the final build (the final build doesn't
>> include RC in the name, does it?), and it's my understanding that only
>> final bits are voted on.
>
> Have a look at the recent number of RC's we've had to do to get our
> releases in shape...
>
> http://people.apache.org/~chirino/
>
> basically we create a maven repo for each RC but the artifacts inside
> them are all 'the final build' with no RC in their name - then if the
> vote goes well, the RC is just moved to the right place. That way we
> don't have to do another build after the vote - but folks can still
> compare each RC etc.
($0.002 from me):
I positively don't like this way.
If I download this build, and unpack it and use it, I have _no idea_ at
a later stager whether it was the proper release or a RC. There might
even be several rounds of RCs, in which case the problem is even worse -
and the final flaw for me using and potentially distributing the wrong
version might be hefty.
I think that a proper RC should be voted on, in which case all jars,
MANIFESTs, tarballs, and toplevel unpack dirs should have a _clear_ RC
in their name, and then if the vote goes through, a _direct rebuild_ of
the release with the content of the preferably _sole file_ denoting the
release's name changed from "<blah>-RC" to "<blah>" should be done and
posted on the official places.
IMHO, of course.
Endre.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by James Strachan <ja...@gmail.com>.
On 11/21/06, Patrick Linskey <pl...@bea.com> wrote:
> What do you do when it comes time to vote? Clearly, you can't be voting
> on the RC build, as that's not the final build (the final build doesn't
> include RC in the name, does it?), and it's my understanding that only
> final bits are voted on.
Have a look at the recent number of RC's we've had to do to get our
releases in shape...
http://people.apache.org/~chirino/
basically we create a maven repo for each RC but the artifacts inside
them are all 'the final build' with no RC in their name - then if the
vote goes well, the RC is just moved to the right place. That way we
don't have to do another build after the vote - but folks can still
compare each RC etc.
--
James
-------
http://radio.weblogs.com/0112098/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by James Strachan <ja...@gmail.com>.
On 11/26/06, Patrick Linskey <pl...@bea.com> wrote:
> So out of curiosity, do you do this just for the incubator release vote,
> or do you go through the same process for the votes on your PMC list as
> well? If the same, do you anticipate going through the same process for
> votes after incubation?
We now use the same process for both. We've tried a few permutations
over the years but for maven 2 releases this seems to work the best so
far.
--
James
-------
http://radio.weblogs.com/0112098/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
RE: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by Patrick Linskey <pl...@bea.com>.
So out of curiosity, do you do this just for the incubator release vote,
or do you go through the same process for the votes on your PMC list as
well? If the same, do you anticipate going through the same process for
votes after incubation?
-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: chirino@gmail.com [mailto:chirino@gmail.com] On Behalf
> Of Hiram Chirino
> Sent: Saturday, November 25, 2006 8:41 AM
> To: general@incubator.apache.org
> Subject: Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
>
> On 11/21/06, Patrick Linskey <pl...@bea.com> wrote:
> > We're doing something pretty much the same; just not calling it
> > RC-anything.
> >
> > What do you do when it comes time to vote? Clearly, you
> can't be voting
> > on the RC build, as that's not the final build (the final
> build doesn't
> > include RC in the name, does it?), and it's my
> understanding that only
> > final bits are voted on.
> >
>
> We just upload the final binaries (without the RC in the name) to a
> directory with an RC-x name in it. Once a given RC-x is finalized we
> copy it's contents to their final resting place.
>
> > -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: chirino@gmail.com [mailto:chirino@gmail.com] On Behalf
> > > Of Hiram Chirino
> > > Sent: Tuesday, November 21, 2006 2:52 PM
> > > To: general@incubator.apache.org
> > > Subject: Re: [VOTE WITHDRAWN] publish openjpa
> 0.9.6-incubating release
> > >
> > > To avoid those issue ActiveMQ tends to do a build of say ActiveMQ
> > > 4.1.0 and we drop it in
> > > a directory called ActiveMQ-4.1.0-RC1 and then if during the vote
> > > something happens, we rebuild and 4.1.0 again and put it
> in directory
> > > called RC2 etc.
> > >
> > > So I would guess you guys just need to put out at
> > > 0.9.6-incubating RC2
> > >
> > > On 11/21/06, Patrick Linskey <pl...@bea.com> wrote:
> > > > > > Hi,
> > > > > >
> > > > > > I agree with Marc that we should continue to iterate on the
> > > > > > 0.9.6-incubating release until we get it right. It
> would only be
> > > > > > confusing if we actually publish the incubating release and
> > > > > then publish
> > > > > > another 0.9.6. But iterations on the release candidate
> > > > > aren't new releases.
> > > > >
> > > > > Yes, but it is confusing if you look at the thread
> about voting on
> > > > > 0.9.6. If 0.9.7 isn't available. Can we have 0.9.6.1
> as the next
> > > > > iteration of the 0.9.6 release?
> > > >
> > > > I don't understand the confusion... 0.9.6 hasn't been
> released yet;
> > > > nobody should be confused by a vote for it.
> > > >
> > > > Personally, I don't much care what we do at this point,
> although I'd
> > > > prefer a 0.9.7 to 0.9.6.1, since there is no 0.9.6
> > > currently and 0.9.6.1
> > > > implies that one does.
> > > >
> > > > However, I *would* like clear guidance about what to do. Is
> > > this going
> > > > to cause problems with incubator approval of the 0.9.6
> vote that's
> > > > currently running on the OpenJPA mailing list?
> > > >
> > > > -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.
> > > >
> > > >
> > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > > For additional commands, e-mail:
> general-help@incubator.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > Regards,
> > > Hiram
> > >
> > > Blog: http://hiramchirino.com
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> > >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by Hiram Chirino <hi...@hiramchirino.com>.
On 11/21/06, Patrick Linskey <pl...@bea.com> wrote:
> We're doing something pretty much the same; just not calling it
> RC-anything.
>
> What do you do when it comes time to vote? Clearly, you can't be voting
> on the RC build, as that's not the final build (the final build doesn't
> include RC in the name, does it?), and it's my understanding that only
> final bits are voted on.
>
We just upload the final binaries (without the RC in the name) to a
directory with an RC-x name in it. Once a given RC-x is finalized we
copy it's contents to their final resting place.
> -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: chirino@gmail.com [mailto:chirino@gmail.com] On Behalf
> > Of Hiram Chirino
> > Sent: Tuesday, November 21, 2006 2:52 PM
> > To: general@incubator.apache.org
> > Subject: Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
> >
> > To avoid those issue ActiveMQ tends to do a build of say ActiveMQ
> > 4.1.0 and we drop it in
> > a directory called ActiveMQ-4.1.0-RC1 and then if during the vote
> > something happens, we rebuild and 4.1.0 again and put it in directory
> > called RC2 etc.
> >
> > So I would guess you guys just need to put out at
> > 0.9.6-incubating RC2
> >
> > On 11/21/06, Patrick Linskey <pl...@bea.com> wrote:
> > > > > Hi,
> > > > >
> > > > > I agree with Marc that we should continue to iterate on the
> > > > > 0.9.6-incubating release until we get it right. It would only be
> > > > > confusing if we actually publish the incubating release and
> > > > then publish
> > > > > another 0.9.6. But iterations on the release candidate
> > > > aren't new releases.
> > > >
> > > > Yes, but it is confusing if you look at the thread about voting on
> > > > 0.9.6. If 0.9.7 isn't available. Can we have 0.9.6.1 as the next
> > > > iteration of the 0.9.6 release?
> > >
> > > I don't understand the confusion... 0.9.6 hasn't been released yet;
> > > nobody should be confused by a vote for it.
> > >
> > > Personally, I don't much care what we do at this point, although I'd
> > > prefer a 0.9.7 to 0.9.6.1, since there is no 0.9.6
> > currently and 0.9.6.1
> > > implies that one does.
> > >
> > > However, I *would* like clear guidance about what to do. Is
> > this going
> > > to cause problems with incubator approval of the 0.9.6 vote that's
> > > currently running on the OpenJPA mailing list?
> > >
> > > -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.
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> > >
> >
> >
> > --
> > Regards,
> > Hiram
> >
> > Blog: http://hiramchirino.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Regards,
Hiram
Blog: http://hiramchirino.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by robert burrell donkin <ro...@gmail.com>.
On 11/22/06, Craig L Russell <Cr...@sun.com> wrote:
> Sorry, I just don't like that changes to the bits based on an
> internal review should change the name of the release.
(there are several reasons why some projects choose to do this but
here's one of mine)
very occasionally such jars escape into the wild and begin to live a
life of their own. sometime very active lives. under these
circumstances it's not uncommon for them to cause lots trouble later.
unique names restrict the damage done.
an academic point in this case, i agree. not trying to persuade
anyone, just offering some background.
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Hiram,
Thanks for the clarification. I understand now how you have decided
to organize your releases.
Craig
On Nov 25, 2006, at 8:38 AM, Hiram Chirino wrote:
> I think you misunderstood me. I agree that release name on the
> release artifact should not change. But there should be some simple
> mechanism so that folks can tell which internal review version you are
> talking about. We just choose to do that by uploading each rebuild of
> the same artifact to a new directory.
>
> On 11/21/06, Craig L Russell <Cr...@sun.com> wrote:
>> Sorry, I just don't like that changes to the bits based on an
>> internal review should change the name of the release.
>>
>> Craig
>>
>> On Nov 21, 2006, at 2:51 PM, Hiram Chirino wrote:
>>
>> > To avoid those issue ActiveMQ tends to do a build of say ActiveMQ
>> > 4.1.0 and we drop it in
>> > a directory called ActiveMQ-4.1.0-RC1 and then if during the vote
>> > something happens, we rebuild and 4.1.0 again and put it in
>> directory
>> > called RC2 etc.
>> >
>> > So I would guess you guys just need to put out at 0.9.6-incubating
>> > RC2
>> >
>> > On 11/21/06, Patrick Linskey <pl...@bea.com> wrote:
>> >> > > Hi,
>> >> > >
>> >> > > I agree with Marc that we should continue to iterate on the
>> >> > > 0.9.6-incubating release until we get it right. It would
>> only be
>> >> > > confusing if we actually publish the incubating release and
>> >> > then publish
>> >> > > another 0.9.6. But iterations on the release candidate
>> >> > aren't new releases.
>> >> >
>> >> > Yes, but it is confusing if you look at the thread about
>> voting on
>> >> > 0.9.6. If 0.9.7 isn't available. Can we have 0.9.6.1 as the next
>> >> > iteration of the 0.9.6 release?
>> >>
>> >> I don't understand the confusion... 0.9.6 hasn't been released
>> yet;
>> >> nobody should be confused by a vote for it.
>> >>
>> >> Personally, I don't much care what we do at this point,
>> although I'd
>> >> prefer a 0.9.7 to 0.9.6.1, since there is no 0.9.6 currently and
>> >> 0.9.6.1
>> >> implies that one does.
>> >>
>> >> However, I *would* like clear guidance about what to do. Is this
>> >> going
>> >> to cause problems with incubator approval of the 0.9.6 vote that's
>> >> currently running on the OpenJPA mailing list?
>> >>
>> >> -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.
>> >>
>> >>
>> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >> For additional commands, e-mail: general-help@incubator.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > Regards,
>> > Hiram
>> >
>> > Blog: http://hiramchirino.com
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> > For additional commands, e-mail: general-help@incubator.apache.org
>> >
>>
>> 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!
>>
>>
>>
>>
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
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: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by Hiram Chirino <hi...@hiramchirino.com>.
I think you misunderstood me. I agree that release name on the
release artifact should not change. But there should be some simple
mechanism so that folks can tell which internal review version you are
talking about. We just choose to do that by uploading each rebuild of
the same artifact to a new directory.
On 11/21/06, Craig L Russell <Cr...@sun.com> wrote:
> Sorry, I just don't like that changes to the bits based on an
> internal review should change the name of the release.
>
> Craig
>
> On Nov 21, 2006, at 2:51 PM, Hiram Chirino wrote:
>
> > To avoid those issue ActiveMQ tends to do a build of say ActiveMQ
> > 4.1.0 and we drop it in
> > a directory called ActiveMQ-4.1.0-RC1 and then if during the vote
> > something happens, we rebuild and 4.1.0 again and put it in directory
> > called RC2 etc.
> >
> > So I would guess you guys just need to put out at 0.9.6-incubating
> > RC2
> >
> > On 11/21/06, Patrick Linskey <pl...@bea.com> wrote:
> >> > > Hi,
> >> > >
> >> > > I agree with Marc that we should continue to iterate on the
> >> > > 0.9.6-incubating release until we get it right. It would only be
> >> > > confusing if we actually publish the incubating release and
> >> > then publish
> >> > > another 0.9.6. But iterations on the release candidate
> >> > aren't new releases.
> >> >
> >> > Yes, but it is confusing if you look at the thread about voting on
> >> > 0.9.6. If 0.9.7 isn't available. Can we have 0.9.6.1 as the next
> >> > iteration of the 0.9.6 release?
> >>
> >> I don't understand the confusion... 0.9.6 hasn't been released yet;
> >> nobody should be confused by a vote for it.
> >>
> >> Personally, I don't much care what we do at this point, although I'd
> >> prefer a 0.9.7 to 0.9.6.1, since there is no 0.9.6 currently and
> >> 0.9.6.1
> >> implies that one does.
> >>
> >> However, I *would* like clear guidance about what to do. Is this
> >> going
> >> to cause problems with incubator approval of the 0.9.6 vote that's
> >> currently running on the OpenJPA mailing list?
> >>
> >> -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.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >>
> >
> >
> > --
> > Regards,
> > Hiram
> >
> > Blog: http://hiramchirino.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
> 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!
>
>
>
>
--
Regards,
Hiram
Blog: http://hiramchirino.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by Craig L Russell <Cr...@Sun.COM>.
Sorry, I just don't like that changes to the bits based on an
internal review should change the name of the release.
Craig
On Nov 21, 2006, at 2:51 PM, Hiram Chirino wrote:
> To avoid those issue ActiveMQ tends to do a build of say ActiveMQ
> 4.1.0 and we drop it in
> a directory called ActiveMQ-4.1.0-RC1 and then if during the vote
> something happens, we rebuild and 4.1.0 again and put it in directory
> called RC2 etc.
>
> So I would guess you guys just need to put out at 0.9.6-incubating
> RC2
>
> On 11/21/06, Patrick Linskey <pl...@bea.com> wrote:
>> > > Hi,
>> > >
>> > > I agree with Marc that we should continue to iterate on the
>> > > 0.9.6-incubating release until we get it right. It would only be
>> > > confusing if we actually publish the incubating release and
>> > then publish
>> > > another 0.9.6. But iterations on the release candidate
>> > aren't new releases.
>> >
>> > Yes, but it is confusing if you look at the thread about voting on
>> > 0.9.6. If 0.9.7 isn't available. Can we have 0.9.6.1 as the next
>> > iteration of the 0.9.6 release?
>>
>> I don't understand the confusion... 0.9.6 hasn't been released yet;
>> nobody should be confused by a vote for it.
>>
>> Personally, I don't much care what we do at this point, although I'd
>> prefer a 0.9.7 to 0.9.6.1, since there is no 0.9.6 currently and
>> 0.9.6.1
>> implies that one does.
>>
>> However, I *would* like clear guidance about what to do. Is this
>> going
>> to cause problems with incubator approval of the 0.9.6 vote that's
>> currently running on the OpenJPA mailing list?
>>
>> -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.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
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: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by Patrick Linskey <pl...@bea.com>.
We're doing something pretty much the same; just not calling it
RC-anything.
What do you do when it comes time to vote? Clearly, you can't be voting
on the RC build, as that's not the final build (the final build doesn't
include RC in the name, does it?), and it's my understanding that only
final bits are voted on.
-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: chirino@gmail.com [mailto:chirino@gmail.com] On Behalf
> Of Hiram Chirino
> Sent: Tuesday, November 21, 2006 2:52 PM
> To: general@incubator.apache.org
> Subject: Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
>
> To avoid those issue ActiveMQ tends to do a build of say ActiveMQ
> 4.1.0 and we drop it in
> a directory called ActiveMQ-4.1.0-RC1 and then if during the vote
> something happens, we rebuild and 4.1.0 again and put it in directory
> called RC2 etc.
>
> So I would guess you guys just need to put out at
> 0.9.6-incubating RC2
>
> On 11/21/06, Patrick Linskey <pl...@bea.com> wrote:
> > > > Hi,
> > > >
> > > > I agree with Marc that we should continue to iterate on the
> > > > 0.9.6-incubating release until we get it right. It would only be
> > > > confusing if we actually publish the incubating release and
> > > then publish
> > > > another 0.9.6. But iterations on the release candidate
> > > aren't new releases.
> > >
> > > Yes, but it is confusing if you look at the thread about voting on
> > > 0.9.6. If 0.9.7 isn't available. Can we have 0.9.6.1 as the next
> > > iteration of the 0.9.6 release?
> >
> > I don't understand the confusion... 0.9.6 hasn't been released yet;
> > nobody should be confused by a vote for it.
> >
> > Personally, I don't much care what we do at this point, although I'd
> > prefer a 0.9.7 to 0.9.6.1, since there is no 0.9.6
> currently and 0.9.6.1
> > implies that one does.
> >
> > However, I *would* like clear guidance about what to do. Is
> this going
> > to cause problems with incubator approval of the 0.9.6 vote that's
> > currently running on the OpenJPA mailing list?
> >
> > -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.
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by Hiram Chirino <hi...@hiramchirino.com>.
To avoid those issue ActiveMQ tends to do a build of say ActiveMQ
4.1.0 and we drop it in
a directory called ActiveMQ-4.1.0-RC1 and then if during the vote
something happens, we rebuild and 4.1.0 again and put it in directory
called RC2 etc.
So I would guess you guys just need to put out at 0.9.6-incubating RC2
On 11/21/06, Patrick Linskey <pl...@bea.com> wrote:
> > > Hi,
> > >
> > > I agree with Marc that we should continue to iterate on the
> > > 0.9.6-incubating release until we get it right. It would only be
> > > confusing if we actually publish the incubating release and
> > then publish
> > > another 0.9.6. But iterations on the release candidate
> > aren't new releases.
> >
> > Yes, but it is confusing if you look at the thread about voting on
> > 0.9.6. If 0.9.7 isn't available. Can we have 0.9.6.1 as the next
> > iteration of the 0.9.6 release?
>
> I don't understand the confusion... 0.9.6 hasn't been released yet;
> nobody should be confused by a vote for it.
>
> Personally, I don't much care what we do at this point, although I'd
> prefer a 0.9.7 to 0.9.6.1, since there is no 0.9.6 currently and 0.9.6.1
> implies that one does.
>
> However, I *would* like clear guidance about what to do. Is this going
> to cause problems with incubator approval of the 0.9.6 vote that's
> currently running on the OpenJPA mailing list?
>
> -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.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Regards,
Hiram
Blog: http://hiramchirino.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Geir Magnusson Jr. wrote:
> Let the podling come up with what they call 0.9.6, let it give clear
> information to what that means, and the incubator PMC votes from there.
Agreed - I was making an observation.
> Patrick Linskey wrote:
>>> Yes, but it is confusing if you look at the thread about voting on
>>> 0.9.6. If 0.9.7 isn't available. Can we have 0.9.6.1 as the next
>>> iteration of the 0.9.6 release?
>>
>> I don't understand the confusion... 0.9.6 hasn't been released yet;
>> nobody should be confused by a vote for it.
If you have openjpa-0.9.6-incubating.tar.gz and openjpa-0.9.6-incubating.tar.gz
- that's where the confusion arises... sure you replaced the package, but it's
the same filename 'over here'. That's the rational for not reusing the same
tarball name, or naming the package before-the-vote as -RC#. Either way, there
is no confusion between the first second third or final/official iteration :)
As Geir says - let the openjpa-dev folk decide, this was just food for thought.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by "Geir Magnusson Jr." <ge...@pobox.com>.
I don't think so.
Let the podling come up with what they call 0.9.6, let it give clear
information to what that means, and the incubator PMC votes from there.
This is getting counterproductive.
geir
Patrick Linskey wrote:
>>> Hi,
>>>
>>> I agree with Marc that we should continue to iterate on the
>>> 0.9.6-incubating release until we get it right. It would only be
>>> confusing if we actually publish the incubating release and
>> then publish
>>> another 0.9.6. But iterations on the release candidate
>> aren't new releases.
>>
>> Yes, but it is confusing if you look at the thread about voting on
>> 0.9.6. If 0.9.7 isn't available. Can we have 0.9.6.1 as the next
>> iteration of the 0.9.6 release?
>
> I don't understand the confusion... 0.9.6 hasn't been released yet;
> nobody should be confused by a vote for it.
>
> Personally, I don't much care what we do at this point, although I'd
> prefer a 0.9.7 to 0.9.6.1, since there is no 0.9.6 currently and 0.9.6.1
> implies that one does.
>
> However, I *would* like clear guidance about what to do. Is this going
> to cause problems with incubator approval of the 0.9.6 vote that's
> currently running on the OpenJPA mailing list?
>
> -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.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Upayavira,
On Nov 21, 2006, at 3:35 PM, Upayavira wrote:
> Patrick Linskey wrote:
>> ...snipped...
>> However, I *would* like clear guidance about what to do. Is this
>> going
>> to cause problems with incubator approval of the 0.9.6 vote that's
>> currently running on the OpenJPA mailing list?
>
> In the end, all you _NEED_ to do is what you are doing. Make a tgz,
> with a specific version. Make it available here. Start a vote.
Done that.
>
> What I'm talking about is more at the level of convenience. You are
> right that 1.9.6 hasn't been released. But a vote has taken place
> for it. Starting another vote for the same release number could
> make it harder for us to differentiate between the two vote threads.
>
> You could simply do [VOTE] 2nd vote for 0.9.6. That would
> successfully differentiate the vote.
Yeah, that's what Marc has done. The subject line for the current
vote is: [VOTE][THIRD ATTEMPT] publish openjpa 0.9.6-incubating release
Should be clear enough that this is the THIRD, yes, THIRD ATTEMPT.
Don't know why all the yelling but bygones. ;-)
Craig
>
> That's all I'm _asking_ for (not demanding).
>
> HTH.
>
> Regards, Upayavira
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
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: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by Upayavira <uv...@odoko.co.uk>.
Patrick Linskey wrote:
>>> Hi,
>>>
>>> I agree with Marc that we should continue to iterate on the
>>> 0.9.6-incubating release until we get it right. It would only be
>>> confusing if we actually publish the incubating release and
>> then publish
>>> another 0.9.6. But iterations on the release candidate
>> aren't new releases.
>>
>> Yes, but it is confusing if you look at the thread about voting on
>> 0.9.6. If 0.9.7 isn't available. Can we have 0.9.6.1 as the next
>> iteration of the 0.9.6 release?
>
> I don't understand the confusion... 0.9.6 hasn't been released yet;
> nobody should be confused by a vote for it.
>
> Personally, I don't much care what we do at this point, although I'd
> prefer a 0.9.7 to 0.9.6.1, since there is no 0.9.6 currently and 0.9.6.1
> implies that one does.
>
> However, I *would* like clear guidance about what to do. Is this going
> to cause problems with incubator approval of the 0.9.6 vote that's
> currently running on the OpenJPA mailing list?
In the end, all you _NEED_ to do is what you are doing. Make a tgz, with
a specific version. Make it available here. Start a vote.
What I'm talking about is more at the level of convenience. You are
right that 1.9.6 hasn't been released. But a vote has taken place for
it. Starting another vote for the same release number could make it
harder for us to differentiate between the two vote threads.
You could simply do [VOTE] 2nd vote for 0.9.6. That would successfully
differentiate the vote.
That's all I'm _asking_ for (not demanding).
HTH.
Regards, Upayavira
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by Leo Simons <ma...@leosimons.com>.
On Nov 21, 2006, at 10:52 PM, Patrick Linskey wrote:
> However, I *would* like clear guidance about what to do.
Do what makes most sense for your developers and your users. It
sounds like you know what that is.
> Is this going
> to cause problems with incubator approval of the 0.9.6 vote that's
> currently running on the OpenJPA mailing list?
No way. As long as you explain the situation so people can do an
informed vote you should be fine.
The day the incubator starts dictating version numbers to podlings is
when I run away screaming :-).
LSD
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
RE: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by "Noel J. Bergman" <no...@devtech.com>.
Patrick,
> Personally, I don't much care what we do at this point, although I'd
> prefer a 0.9.7 to 0.9.6.1
> However, I *would* like clear guidance about what to do.
Figuring this out is something that the PPMC ought to deal with. You have
had several suggestions made to you, and one of the things that *I'd* like
to see is how you folks deal with it.
FWIW, I, personally, do not really care what outcome you come to, so much as
I care to see how you come to a conclusion. Think of me as the Philosophy
Professor from school who doesn't care which side of the debate you argue,
but does care about the argument, itself. :-)
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
RE: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by Patrick Linskey <pl...@bea.com>.
> > Hi,
> >
> > I agree with Marc that we should continue to iterate on the
> > 0.9.6-incubating release until we get it right. It would only be
> > confusing if we actually publish the incubating release and
> then publish
> > another 0.9.6. But iterations on the release candidate
> aren't new releases.
>
> Yes, but it is confusing if you look at the thread about voting on
> 0.9.6. If 0.9.7 isn't available. Can we have 0.9.6.1 as the next
> iteration of the 0.9.6 release?
I don't understand the confusion... 0.9.6 hasn't been released yet;
nobody should be confused by a vote for it.
Personally, I don't much care what we do at this point, although I'd
prefer a 0.9.7 to 0.9.6.1, since there is no 0.9.6 currently and 0.9.6.1
implies that one does.
However, I *would* like clear guidance about what to do. Is this going
to cause problems with incubator approval of the 0.9.6 vote that's
currently running on the OpenJPA mailing list?
-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.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by Upayavira <uv...@odoko.co.uk>.
Craig L Russell wrote:
> Hi,
>
> I agree with Marc that we should continue to iterate on the
> 0.9.6-incubating release until we get it right. It would only be
> confusing if we actually publish the incubating release and then publish
> another 0.9.6. But iterations on the release candidate aren't new releases.
Yes, but it is confusing if you look at the thread about voting on
0.9.6. If 0.9.7 isn't available. Can we have 0.9.6.1 as the next
iteration of the 0.9.6 release?
Upayavira
> On Nov 21, 2006, at 8:16 AM, Marc Prud'hommeaux wrote:
>
>> William
>>
>> Good point, but since the trunk (from which
>> "0.9.7-incubating-SNAPSHOT" nighties are being built) has advanced
>> with potentially destabilizing changes since the branch point
>> "0.9.6-incubating", it might be even more confusing for anyone who is
>> relying on "0.9.7-incubating-SNAPSHOT" changes to see them suddenly
>> gone in a subsequent "0.9.7-incubating" release. We'd rather fix the
>> issues with the licenses and other miscellaneous issues and get the
>> release out the door without introducing the risk of new and changed
>> code causing unnecessary problems and further delays.
>>
>>
>>
>> On Nov 21, 2006, at 5:44 AM, William A. Rowe, Jr. wrote:
>>
>>> Marc Prud'hommeaux wrote:
>>>>
>>>> For the purposes of closure, I am officially withdrawing this vote for
>>>> the openjpa 0.9.6-incubating release while we make the changes that
>>>> Robert mentions.
>>>>
>>>> We expect that a new vote will be started for the 0.9.6-incubating
>>>> release
>>>
>>> Remember version numbers are *cheap* - burn one. It resolves confusion
>>> over 'which 0.9.6 is the problem?' 0.9.7, .8, .9, .10 etc can always
>>> follow (and is a good sign the releases are being triple checked when
>>> versions end up begin skipped.)
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> 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!
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi,
I agree with Marc that we should continue to iterate on the 0.9.6-
incubating release until we get it right. It would only be confusing
if we actually publish the incubating release and then publish
another 0.9.6. But iterations on the release candidate aren't new
releases.
Craig
On Nov 21, 2006, at 8:16 AM, Marc Prud'hommeaux wrote:
> William
>
> Good point, but since the trunk (from which "0.9.7-incubating-
> SNAPSHOT" nighties are being built) has advanced with potentially
> destabilizing changes since the branch point "0.9.6-incubating", it
> might be even more confusing for anyone who is relying on "0.9.7-
> incubating-SNAPSHOT" changes to see them suddenly gone in a
> subsequent "0.9.7-incubating" release. We'd rather fix the issues
> with the licenses and other miscellaneous issues and get the
> release out the door without introducing the risk of new and
> changed code causing unnecessary problems and further delays.
>
>
>
> On Nov 21, 2006, at 5:44 AM, William A. Rowe, Jr. wrote:
>
>> Marc Prud'hommeaux wrote:
>>>
>>> For the purposes of closure, I am officially withdrawing this
>>> vote for
>>> the openjpa 0.9.6-incubating release while we make the changes that
>>> Robert mentions.
>>>
>>> We expect that a new vote will be started for the 0.9.6-incubating
>>> release
>>
>> Remember version numbers are *cheap* - burn one. It resolves
>> confusion
>> over 'which 0.9.6 is the problem?' 0.9.7, .8, .9, .10 etc can always
>> follow (and is a good sign the releases are being triple checked when
>> versions end up begin skipped.)
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
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: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by Marc Prud'hommeaux <mp...@apache.org>.
William
Good point, but since the trunk (from which "0.9.7-incubating-
SNAPSHOT" nighties are being built) has advanced with potentially
destabilizing changes since the branch point "0.9.6-incubating", it
might be even more confusing for anyone who is relying on "0.9.7-
incubating-SNAPSHOT" changes to see them suddenly gone in a
subsequent "0.9.7-incubating" release. We'd rather fix the issues
with the licenses and other miscellaneous issues and get the release
out the door without introducing the risk of new and changed code
causing unnecessary problems and further delays.
On Nov 21, 2006, at 5:44 AM, William A. Rowe, Jr. wrote:
> Marc Prud'hommeaux wrote:
>>
>> For the purposes of closure, I am officially withdrawing this vote
>> for
>> the openjpa 0.9.6-incubating release while we make the changes that
>> Robert mentions.
>>
>> We expect that a new vote will be started for the 0.9.6-incubating
>> release
>
> Remember version numbers are *cheap* - burn one. It resolves
> confusion
> over 'which 0.9.6 is the problem?' 0.9.7, .8, .9, .10 etc can always
> follow (and is a good sign the releases are being triple checked when
> versions end up begin skipped.)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Marc Prud'hommeaux wrote:
>
> For the purposes of closure, I am officially withdrawing this vote for
> the openjpa 0.9.6-incubating release while we make the changes that
> Robert mentions.
>
> We expect that a new vote will be started for the 0.9.6-incubating
> release
Remember version numbers are *cheap* - burn one. It resolves confusion
over 'which 0.9.6 is the problem?' 0.9.7, .8, .9, .10 etc can always
follow (and is a good sign the releases are being triple checked when
versions end up begin skipped.)
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
[VOTE WITHDRAWN] publish openjpa 0.9.6-incubating release
Posted by Marc Prud'hommeaux <mp...@apache.org>.
For the purposes of closure, I am officially withdrawing this vote
for the openjpa 0.9.6-incubating release while we make the changes
that Robert mentions.
We expect that a new vote will be started for the 0.9.6-incubating
release tonight or tomorrow.
Thanks very much to Robert for all the useful feedback and guidance
while we work towards getting an initial release of OpenJPA out the
door!
On Nov 18, 2006, at 2:00 PM, robert burrell donkin wrote:
> On 11/18/06, Craig L Russell <Cr...@sun.com> wrote:
>> The file is in the persistence-api component.
>>
>> https://glassfish.dev.java.net/source/browse/glassfish/persistence-
>> api/schemas/persistence_1_0.xsd?view=markup
>>
>> The xsd file in question is licensed under the terms of the CDDL
>> license under which we already distribute the persistence jar file.
>>
>> http://wiki.java.net/bin/view/Projects/GlassFishCodeDependencies
>>
>> I think we're good to go with this file. The only thing to consider
>> is if we need to update the LICENSE file to call out that this file
>> is associated with this license.
>
> yes please
>
> (this is neat illustration of the reason why the LICENSE file contains
> this information: it's hard enough to work out now. five years down
> the line, it would probably take considerable effort to track this
> information down. apache releases are long lived and licensing
> questions occasionally crop up about code that is over five years
> old.)
>
> thanks for tracking this one down
>
> - robert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by robert burrell donkin <ro...@gmail.com>.
On 11/18/06, Craig L Russell <Cr...@sun.com> wrote:
> The file is in the persistence-api component.
>
> https://glassfish.dev.java.net/source/browse/glassfish/persistence-
> api/schemas/persistence_1_0.xsd?view=markup
>
> The xsd file in question is licensed under the terms of the CDDL
> license under which we already distribute the persistence jar file.
>
> http://wiki.java.net/bin/view/Projects/GlassFishCodeDependencies
>
> I think we're good to go with this file. The only thing to consider
> is if we need to update the LICENSE file to call out that this file
> is associated with this license.
yes please
(this is neat illustration of the reason why the LICENSE file contains
this information: it's hard enough to work out now. five years down
the line, it would probably take considerable effort to track this
information down. apache releases are long lived and licensing
questions occasionally crop up about code that is over five years
old.)
thanks for tracking this one down
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by Craig L Russell <Cr...@Sun.COM>.
The file is in the persistence-api component.
https://glassfish.dev.java.net/source/browse/glassfish/persistence-
api/schemas/persistence_1_0.xsd?view=markup
The xsd file in question is licensed under the terms of the CDDL
license under which we already distribute the persistence jar file.
http://wiki.java.net/bin/view/Projects/GlassFishCodeDependencies
I think we're good to go with this file. The only thing to consider
is if we need to update the LICENSE file to call out that this file
is associated with this license.
Craig
On Nov 18, 2006, at 6:49 AM, robert burrell donkin wrote:
>> I'm not sure what to do about that one ... it is a cached copy of
>> http://java.sun.com/xml/ns/persistence/orm_1_0.xsd which we use for
>> XML schema validation without having to go to the web (which would be
>> prohibitive). The original schema doesn't specify any license, and
>> I'm not sure what the implicit license would be, but I also wouldn't
>> feel right about sticking in an Apache license header for a file that
>> we obviously didn't create.
>
> exactly right: never just stick headers in anything without clear
> provinence
>
>> Any thoughts?
>
> in the absence of any clear license, there is a link at the bottom of
> http://java.sun.com/xml/ns/persistence/ which says
> http://developers.sun.com/license/berkeley_license.html. arguable,
> though, it's part of the RI which is probably LGPL'd.
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: Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by robert burrell donkin <ro...@gmail.com>.
On 11/17/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
> On Nov 16, 2006, at 12:57 PM, robert burrell donkin wrote:
> > On 11/16/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
<snip>
> > i have some issues i'd like to see fixed plus less important issues,
> > some questions i'd like answered and some comments just FYI
> >
> > -- issues (i would like to see fixed) --
<snip>
> > openjpa distributes some jars in the binary. NOTICE.txt is ok (but
> > note http://www.apache.org/legal/src-headers.html now asks that apache
> > collective copyright is included) but their licenses are not included
> > in LICENSE.txt. see
> > http://incubator.apache.org/guides/examples/LICENSE for example.
>
> The only two non-ASF jars in the distribution are serp-1.11.0.jar
> (BSD license) and persistence-api-1.0.jar (Sun CDDL). I've added
> their licenses into our LICENSE.txt. I'd appreciate if you could take
> a glance at the text (at https://svn.apache.org/repos/asf/incubator/
> openjpa/trunk/openjpa-project/LICENSE.txt ) and let me know if that
> looks sufficient.
looks good :-)
> Also, I don't think I need to add the licenses for the ASF jars that
> are included with the binaries. If I'm incorrect about that, please
> let me know, and I'll paste in the text of their identical licenses
> to our LICENSE.txt file.
no need to add duplicate copies of each particular LICENSE
the aim is to inform downstream users in particular packages about the
LICENSE for each artifact distributed. this is good for both legal and
social reasons. it's up to the project how they achieve this goal.
there are other acceptable ways used but the example is a commonly
used approach.
> > source distribution is missing LICENSE, NOTICE and DISCLAIMER at the
> > top level. (these probably need to be commit into svn.)
>
> As an exact snapshot of the buildable sources, these files were
> included in the "openjpa-project" sub-directory of the sources
> package. Reviewing http://www.apache.org/legal/src-
> headers.html#notice , I see that they need to be included in the top
> directory of any artifact, so I've added a directive to the source
> distribution build to add them there.
(i personally distrust source distribution processing of any kind. i
worry about reproducability. but this is a matter for the project so)
that should be ok
> > -- minor issues --
> >
> > http://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-
> > incubating/src/site/apt/*.apt
> > lack license headers. apt supports comments so these should probably
> > have headers.
>
> I've added license headers to these files. I hadn't realized that apt
> supported comments.
seems to be an under-advertised feature :-)
> > -- questions --
> >
> > i can't find LICENSE, NOTICE or DISCLAIMER in
> > openjpa-all-0.9.6-incubating.jar. did you intend to prevent official
> > distribution through maven repositories?
>
> Oops ... we missed putting these in. I've corrected this for the
> LICENSE.txt and NOTICE.txt files. However, looking at http://
> www.apache.org/legal/src-headers.html#faq-binaries , I don't see any
> mention of including the DISCLAIMER file ... is there somewhere else
> that mentions that that file should be included in jars (or other
> binary artifacts)?
you won't find it since this is not a general requirement for apache
releases :-)
the IPMC requires a disclaimer text is distributed with each artifact.
i guessed that since openjpa uses a DISCLAIMER.txt that it would make
sense to include this. feel free to shoot me down if you already
include the disclaimer in some other form.
> > (RAT)
> >
> > http://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-
> > incubating/openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/
> > schema/schemas-doctype.rsrc
> > has no license header. is this a generated file?
>
> No, but I don't think the format supports comments.
i'm going to assume that it's a DTD
AIUI it's possible to include xml style comments (<!-- -->) in all
parsed entities (those that start with a prolog for example <?xml
version='1.0'?>) but i'm willing to stand corrected...
this isn't a release stopper for me
> > http://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-
> > incubating/openjpa-persistence/src/main/resources/org/apache/
> > openjpa/persistence/orm-xsd.rsrc
> > has no license header. is this a generated file?
>
> I'm not sure what to do about that one ... it is a cached copy of
> http://java.sun.com/xml/ns/persistence/orm_1_0.xsd which we use for
> XML schema validation without having to go to the web (which would be
> prohibitive). The original schema doesn't specify any license, and
> I'm not sure what the implicit license would be, but I also wouldn't
> feel right about sticking in an Apache license header for a file that
> we obviously didn't create.
exactly right: never just stick headers in anything without clear provinence
> Any thoughts?
in the absence of any clear license, there is a link at the bottom of
http://java.sun.com/xml/ns/persistence/ which says
http://developers.sun.com/license/berkeley_license.html. arguable,
though, it's part of the RI which is probably LGPL'd.
but all this seems far too flimsy for comfort
i recommend taking this up on legal-discuss and (if possible)
contacting sun directly for clear guidance about their intended
license. it would be cleaner and clearer if they embedded the license
in the document or (at least) included the information in
http://java.sun.com/xml/ns/persistence.
unfortunately, this sounds like it might take a while to sort out :-/
might be quicker just to create a clean room implementation direct
from the specification
> > -- comments --
> >
> > --- notes and suggestions (for future reference) ---
> >
> > there is no need to create sums for detached signatures.
>
> Maven seems to automatically attach .md5 and .sha1 checksums to all
> uploaded artifacts. Since we are generating the .asc signatures in
> the Maven process, it seems to include these in the list of artifacts
> to sign. There doesn't seem to be any way to disable this, and the
> convenience gained by having these files generated and uploaded as
> part of the Maven build process outweighed the annoyance of having
> these vestigial checksums lying around (IMO).
fine
> > some users (typically on *nix) prefer either bz2'd or tar.gz's
> > distributions. creating additional artifacts is quick and easy so this
> > is an easy way to make life just a little easier for some users.
>
> We briefly discussed this on the open-jpa-list. While it is certainly
> de-facto convention to release under both .zip and .tar.gz packaging
> types, the only compelling reason to do so appears to be that UNIX
> executable permissions are lost in the zip format. Since we don't
> have any executables in the openjpa distribution, there doesn't seem
> to be much reason to have additional packaging formats.
>
> We'd be interested in knowing if there are other advantages to having
> multiple packaging mechanisms, though.
releases are important guerrilla advertising for a project :-)
user expectation and convenience. users expect projects that produce
just zip'd distributions to be windows centric. distributions with
alternative compression are easy and quick to produce. so IMHO it
makes sense to distribute .tar.gz'd as well as zip'd just to make
*nix'ers feel at home. good for linux-centric grassroots news channels
(such as freshmeat) as well.
but it's for the community to decide so it's the debate that's important
<snip>
> > there is no RELEASE_NOTES in the base directory. for open source
> > projects, these serve as an important communication to users. the
> > content will often serve for reuse in announcements and other
> > grassroots publicity. consider creating them for the next release.
>
> We don't have one since this is our initial release, so the whole
> package is effectively one big release note :)
RELEASE_NOTES are important guerrilla advertising for a project :-)
the content is often reused for announcements and for grassroots news
channels such as freshmeat. release notes should describe a project's
purpose and aims, how people can get involved, list sources of
information and give some general information about the project's
plans.
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by Marc Prud'hommeaux <mp...@apache.org>.
Robert-
We'll correct these issues asap. Once corrected artifacts are
uploaded, I assume it will necessary to re-start the vote on the open-
jpa-dev list before re-starting the vote here. Please correct me if I
am wrong.
Responses to specific points are inline below...
On Nov 16, 2006, at 12:57 PM, robert burrell donkin wrote:
> On 11/16/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
>>
>> The OpenJPA incubator community voted on and has approved a proposal
>> to release OpenJPA 0.9.6-incubating. Pursuant to the Releases section
>> of the Incubation Policy (http://incubator.apache.org/incubation/
>> Incubation_Policy.html#Releases ) we would now like to request the
>> permission of the Incubator PMC to publish the release zip file on
>> the openjpa download page (http://cwiki.apache.org/openjpa/
>> downloads.html).
>
> i have some issues i'd like to see fixed plus less important issues,
> some questions i'd like answered and some comments just FYI
>
> -- issues (i would like to see fixed) --
>
> http://incubator.apache.org/projects/openjpa.html has some unresolved
> copyright issues. i trust that this just means that the status page
> hasn't been updated.
I believe that the page just needs to be updated. I'll follow-up on
the open-jpa-dev list to find out how to go about doing this.
> openjpa distributes some jars in the binary. NOTICE.txt is ok (but
> note http://www.apache.org/legal/src-headers.html now asks that apache
> collective copyright is included) but their licenses are not included
> in LICENSE.txt. see
> http://incubator.apache.org/guides/examples/LICENSE for example.
The only two non-ASF jars in the distribution are serp-1.11.0.jar
(BSD license) and persistence-api-1.0.jar (Sun CDDL). I've added
their licenses into our LICENSE.txt. I'd appreciate if you could take
a glance at the text (at https://svn.apache.org/repos/asf/incubator/
openjpa/trunk/openjpa-project/LICENSE.txt ) and let me know if that
looks sufficient.
Also, I don't think I need to add the licenses for the ASF jars that
are included with the binaries. If I'm incorrect about that, please
let me know, and I'll paste in the text of their identical licenses
to our LICENSE.txt file.
> source distribution is missing LICENSE, NOTICE and DISCLAIMER at the
> top level. (these probably need to be commit into svn.)
As an exact snapshot of the buildable sources, these files were
included in the "openjpa-project" sub-directory of the sources
package. Reviewing http://www.apache.org/legal/src-
headers.html#notice , I see that they need to be included in the top
directory of any artifact, so I've added a directive to the source
distribution build to add them there.
> -- minor issues --
>
> http://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-
> incubating/src/site/apt/*.apt
> lack license headers. apt supports comments so these should probably
> have headers.
I've added license headers to these files. I hadn't realized that apt
supported comments.
> -- questions --
>
> i can't find LICENSE, NOTICE or DISCLAIMER in
> openjpa-all-0.9.6-incubating.jar. did you intend to prevent official
> distribution through maven repositories?
Oops ... we missed putting these in. I've corrected this for the
LICENSE.txt and NOTICE.txt files. However, looking at http://
www.apache.org/legal/src-headers.html#faq-binaries , I don't see any
mention of including the DISCLAIMER file ... is there somewhere else
that mentions that that file should be included in jars (or other
binary artifacts)?
> (RAT)
>
> http://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-
> incubating/openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/
> schema/schemas-doctype.rsrc
> has no license header. is this a generated file?
No, but I don't think the format supports comments.
> http://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-
> incubating/openjpa-persistence/src/main/resources/org/apache/
> openjpa/persistence/orm-xsd.rsrc
> has no license header. is this a generated file?
I'm not sure what to do about that one ... it is a cached copy of
http://java.sun.com/xml/ns/persistence/orm_1_0.xsd which we use for
XML schema validation without having to go to the web (which would be
prohibitive). The original schema doesn't specify any license, and
I'm not sure what the implicit license would be, but I also wouldn't
feel right about sticking in an Apache license header for a file that
we obviously didn't create.
Any thoughts?
> -- comments --
>
> --- notes and suggestions (for future reference) ---
>
> there is no need to create sums for detached signatures.
Maven seems to automatically attach .md5 and .sha1 checksums to all
uploaded artifacts. Since we are generating the .asc signatures in
the Maven process, it seems to include these in the list of artifacts
to sign. There doesn't seem to be any way to disable this, and the
convenience gained by having these files generated and uploaded as
part of the Maven build process outweighed the annoyance of having
these vestigial checksums lying around (IMO).
> some users (typically on *nix) prefer either bz2'd or tar.gz's
> distributions. creating additional artifacts is quick and easy so this
> is an easy way to make life just a little easier for some users.
We briefly discussed this on the open-jpa-list. While it is certainly
de-facto convention to release under both .zip and .tar.gz packaging
types, the only compelling reason to do so appears to be that UNIX
executable permissions are lost in the zip format. Since we don't
have any executables in the openjpa distribution, there doesn't seem
to be much reason to have additional packaging formats.
We'd be interested in knowing if there are other advantages to having
multiple packaging mechanisms, though.
> i personally prefer the source and binary distributions to unpack to
> different directories but the overlay style (both unpack to the same
> directory forming a combined product) is also good if a little effort
> is invested into it.
This request was also made on the open-jpa-dev list. I've gone ahead
and made the source assembly unpack to a different parent directory.
> there is no RELEASE_NOTES in the base directory. for open source
> projects, these serve as an important communication to users. the
> content will often serve for reuse in announcements and other
> grassroots publicity. consider creating them for the next release.
We don't have one since this is our initial release, so the whole
package is effectively one big release note :)
> - robert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by Craig L Russell <Cr...@Sun.COM>.
From my experience on the incubator list, this is probably the most
complete critique that we will get. So I think we're done once Robert
is happy.
Craig
On Nov 16, 2006, at 2:16 PM, Patrick Linskey wrote:
> Hi,
>
> Does anyone else have any showstopping concerns? It'd be good to know
> about them now, so that we can fix all of them and then re-run the
> three-day vote on the OpenJPA list.
>
> Thanks,
>
> -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: robert burrell donkin [mailto:robertburrelldonkin@gmail.com]
>> Sent: Thursday, November 16, 2006 12:58 PM
>> To: general@incubator.apache.org
>> Subject: Re: [VOTE] publish openjpa 0.9.6-incubating release
>>
>> On 11/16/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
>>>
>>> The OpenJPA incubator community voted on and has approved a proposal
>>> to release OpenJPA 0.9.6-incubating. Pursuant to the
>> Releases section
>>> of the Incubation Policy (http://incubator.apache.org/incubation/
>>> Incubation_Policy.html#Releases ) we would now like to request the
>>> permission of the Incubator PMC to publish the release zip file on
>>> the openjpa download page (http://cwiki.apache.org/openjpa/
>>> downloads.html).
>>
>> i have some issues i'd like to see fixed plus less important issues,
>> some questions i'd like answered and some comments just FYI
>>
>> -- issues (i would like to see fixed) --
>>
>> http://incubator.apache.org/projects/openjpa.html has some unresolved
>> copyright issues. i trust that this just means that the status page
>> hasn't been updated.
>>
>> openjpa distributes some jars in the binary. NOTICE.txt is ok (but
>> note http://www.apache.org/legal/src-headers.html now asks that
>> apache
>> collective copyright is included) but their licenses are not included
>> in LICENSE.txt. see
>> http://incubator.apache.org/guides/examples/LICENSE for example.
>>
>> source distribution is missing LICENSE, NOTICE and DISCLAIMER at the
>> top level. (these probably need to be commit into svn.)
>>
>> -- minor issues --
>>
>> http://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-i
> ncubating/src/site/apt/*.apt
>> lack license headers. apt supports comments so these should probably
>> have headers.
>>
>> -- questions --
>>
>> i can't find LICENSE, NOTICE or DISCLAIMER in
>> openjpa-all-0.9.6-incubating.jar. did you intend to prevent official
>> distribution through maven repositories?
>>
>> (RAT)
>>
>> http://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-i
> ncubating/openjpa->
> jdbc/src/main/resources/org/apache/openjpa/jdbc/schema/schemas
>> -doctype.rsrc
>> has no license header. is this a generated file?
>>
>> http://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-i
> ncubating/openjpa->
> persistence/src/main/resources/org/apache/openjpa/persistence/
>> orm-xsd.rsrc
>> has no license header. is this a generated file?
>>
>> -- comments --
>>
>> --- notes and suggestions (for future reference) ---
>>
>> there is no need to create sums for detached signatures.
>>
>> some users (typically on *nix) prefer either bz2'd or tar.gz's
>> distributions. creating additional artifacts is quick and easy so
>> this
>> is an easy way to make life just a little easier for some users.
>>
>> i personally prefer the source and binary distributions to unpack to
>> different directories but the overlay style (both unpack to the same
>> directory forming a combined product) is also good if a little effort
>> is invested into it.
>>
>> there is no RELEASE_NOTES in the base directory. for open source
>> projects, these serve as an important communication to users. the
>> content will often serve for reuse in announcements and other
>> grassroots publicity. consider creating them for the next release.
>>
>> - robert
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
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: [VOTE] publish openjpa 0.9.6-incubating release
Posted by Patrick Linskey <pl...@bea.com>.
Hi,
Does anyone else have any showstopping concerns? It'd be good to know
about them now, so that we can fix all of them and then re-run the
three-day vote on the OpenJPA list.
Thanks,
-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: robert burrell donkin [mailto:robertburrelldonkin@gmail.com]
> Sent: Thursday, November 16, 2006 12:58 PM
> To: general@incubator.apache.org
> Subject: Re: [VOTE] publish openjpa 0.9.6-incubating release
>
> On 11/16/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
> >
> > The OpenJPA incubator community voted on and has approved a proposal
> > to release OpenJPA 0.9.6-incubating. Pursuant to the
> Releases section
> > of the Incubation Policy (http://incubator.apache.org/incubation/
> > Incubation_Policy.html#Releases ) we would now like to request the
> > permission of the Incubator PMC to publish the release zip file on
> > the openjpa download page (http://cwiki.apache.org/openjpa/
> > downloads.html).
>
> i have some issues i'd like to see fixed plus less important issues,
> some questions i'd like answered and some comments just FYI
>
> -- issues (i would like to see fixed) --
>
> http://incubator.apache.org/projects/openjpa.html has some unresolved
> copyright issues. i trust that this just means that the status page
> hasn't been updated.
>
> openjpa distributes some jars in the binary. NOTICE.txt is ok (but
> note http://www.apache.org/legal/src-headers.html now asks that apache
> collective copyright is included) but their licenses are not included
> in LICENSE.txt. see
> http://incubator.apache.org/guides/examples/LICENSE for example.
>
> source distribution is missing LICENSE, NOTICE and DISCLAIMER at the
> top level. (these probably need to be commit into svn.)
>
> -- minor issues --
>
> http://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-i
ncubating/src/site/apt/*.apt
> lack license headers. apt supports comments so these should probably
> have headers.
>
> -- questions --
>
> i can't find LICENSE, NOTICE or DISCLAIMER in
> openjpa-all-0.9.6-incubating.jar. did you intend to prevent official
> distribution through maven repositories?
>
> (RAT)
>
> http://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-i
ncubating/openjpa->
jdbc/src/main/resources/org/apache/openjpa/jdbc/schema/schemas
> -doctype.rsrc
> has no license header. is this a generated file?
>
> http://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-i
ncubating/openjpa->
persistence/src/main/resources/org/apache/openjpa/persistence/
> orm-xsd.rsrc
> has no license header. is this a generated file?
>
> -- comments --
>
> --- notes and suggestions (for future reference) ---
>
> there is no need to create sums for detached signatures.
>
> some users (typically on *nix) prefer either bz2'd or tar.gz's
> distributions. creating additional artifacts is quick and easy so this
> is an easy way to make life just a little easier for some users.
>
> i personally prefer the source and binary distributions to unpack to
> different directories but the overlay style (both unpack to the same
> directory forming a combined product) is also good if a little effort
> is invested into it.
>
> there is no RELEASE_NOTES in the base directory. for open source
> projects, these serve as an important communication to users. the
> content will often serve for reuse in announcements and other
> grassroots publicity. consider creating them for the next release.
>
> - robert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] publish openjpa 0.9.6-incubating release
Posted by robert burrell donkin <ro...@gmail.com>.
On 11/16/06, Marc Prud'hommeaux <mp...@apache.org> wrote:
>
> The OpenJPA incubator community voted on and has approved a proposal
> to release OpenJPA 0.9.6-incubating. Pursuant to the Releases section
> of the Incubation Policy (http://incubator.apache.org/incubation/
> Incubation_Policy.html#Releases ) we would now like to request the
> permission of the Incubator PMC to publish the release zip file on
> the openjpa download page (http://cwiki.apache.org/openjpa/
> downloads.html).
i have some issues i'd like to see fixed plus less important issues,
some questions i'd like answered and some comments just FYI
-- issues (i would like to see fixed) --
http://incubator.apache.org/projects/openjpa.html has some unresolved
copyright issues. i trust that this just means that the status page
hasn't been updated.
openjpa distributes some jars in the binary. NOTICE.txt is ok (but
note http://www.apache.org/legal/src-headers.html now asks that apache
collective copyright is included) but their licenses are not included
in LICENSE.txt. see
http://incubator.apache.org/guides/examples/LICENSE for example.
source distribution is missing LICENSE, NOTICE and DISCLAIMER at the
top level. (these probably need to be commit into svn.)
-- minor issues --
http://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-incubating/src/site/apt/*.apt
lack license headers. apt supports comments so these should probably
have headers.
-- questions --
i can't find LICENSE, NOTICE or DISCLAIMER in
openjpa-all-0.9.6-incubating.jar. did you intend to prevent official
distribution through maven repositories?
(RAT)
http://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-incubating/openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/schema/schemas-doctype.rsrc
has no license header. is this a generated file?
http://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-incubating/openjpa-persistence/src/main/resources/org/apache/openjpa/persistence/orm-xsd.rsrc
has no license header. is this a generated file?
-- comments --
--- notes and suggestions (for future reference) ---
there is no need to create sums for detached signatures.
some users (typically on *nix) prefer either bz2'd or tar.gz's
distributions. creating additional artifacts is quick and easy so this
is an easy way to make life just a little easier for some users.
i personally prefer the source and binary distributions to unpack to
different directories but the overlay style (both unpack to the same
directory forming a combined product) is also good if a little effort
is invested into it.
there is no RELEASE_NOTES in the base directory. for open source
projects, these serve as an important communication to users. the
content will often serve for reuse in announcements and other
grassroots publicity. consider creating them for the next release.
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org