For the record, I'm still +1 for release.
But if you want to cut another to fix the minor items that have been surfaced, it's ok with me.
Craig On Apr 18, 2007, at 11:42 AM, Eddie O'Neil wrote:
Mike-- RE the KEYS file, you can just ssh to people.apache.org and check the KEYS file out directly into /www/incubator.apache.org/openjpa/ directory. No uploading necessary! :) To be sure -- the rest of the items are just nits which could mostly be cleaned up just by deleting the directories / files after they're uploaded. I don't have strong feelings about them, so just do whatever the community feels is best. Certainly, it's fine to ship them for 0.9.7. Cheers, Eddie On 4/18/07, Michael Dick <[EMAIL PROTECTED]> wrote:Thanks Marc,How do I upload my key to http://incubator.apache.org/openjpa/ KEYS ? The only documentation I've found indicates that I need to upload it, but notwhere the key needs to go.Before I create another release candidate (to remove the docbook jar), should we try to address the other minor issues? Craig and Patrick haveresponded to most of them, but there are a few others. Minor issues: - The .zip distribution contains .asc files for the .md5 and .sha1 > files, which are unnecessary.They're unnecessary, but I've been ignoring them since they aren't hurting anything. It isn't too hard to get rid of them though. I think the gpgplugin for maven signs the .md5 and sha1 files too (I'd have to check though). - The source distribution contains a derby.log file at: > <source-dist>/openjpa-persistence-jdbc/derby.logThis is pretty easy to clean up, and I'll do that before I create anotherrelease candidate.The other issues Craig and Patrick have responded to. If any of them can befixed quickly then we can include them in the new release candidate. On 4/18/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote: > > >> Good idea ... I've gone ahead and done that. It should make things a> little easier to manage. > > > > On Apr 18, 2007, at 10:45 AM, Patrick Linskey wrote: > > >> This is there because we draw in all the dependencies that we > >> don't explicitly exclude in the openjpa-project/assembly.xml, > >> and at some point, someone (probably me) added docbook-xsl as > >> a dependency so as to ensure that the docbook processing > >> phase had access to the stylesheets. > > > > Is it possible to invert that, so that we only include certain > > dependencies? > > > > -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: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On > >> Behalf Of Marc Prud'hommeaux > >> Sent: Wednesday, April 18, 2007 10:23 AM > >> To: open-jpa-dev@incubator.apache.org > >> Subject: Re: [VOTE] publish openjpa 0.9.7-incubating release > >> > >> > >> On Apr 18, 2007, at 10:11 AM, Patrick Linskey wrote: > >>> >>>> - The binary distribution contains a new JAR file whose license is> >>>> unclear; this is: > >>>> <binary-dist>/lib/docbook-xsl-1.67.2.zip > >>> > >>> That dependency is unnecessary -- it's needed to build the > >> docs, but > >>> not by the runtime. > >> > >> This is there because we draw in all the dependencies that we > >> don't explicitly exclude in the openjpa-project/assembly.xml, > >> and at some point, someone (probably me) added docbook-xsl as > >> a dependency so as to ensure that the docbook processing > >> phase had access to the stylesheets. > >> > >> I've gone ahead and fixed this in the trunk by adding it to > >> the exclude list (revision 530094). > >> > >> > >> > >> > >> > > > > 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.> > -- -Michael Dick
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature