Agreed. I'll go further and nominate "someone not employed by BEA, unless it's Eddie, who doesn't do hands-on OpenJPA coding in his day job".
-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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, November 10, 2006 6:47 PM > To: firstname.lastname@example.org > Subject: Re: How to build an OpenJPA release > > I'd like to see "someone else" build the next OpenJPA release > following Marc's excellent documented process. > > That might actually prevent a Marc-bus interaction by the umbrella- > rain postulate. ;-) > > Craig > > On Nov 10, 2006, at 4:06 PM, Marc Prud'hommeaux wrote: > > > OpenJPA People- > > > > In keeping with the "hit by a bus" philosophy of defensive > > documentation, I've documented the steps that I took to build and > > upload the OpenJPA release. > > > > In case anyone is interested, it is available here: > > > > http://cwiki.apache.org/openjpa/releasing-openjpa.html > > > > Please feel free to update the page if you see any errors or > > omissions. > > > > > > 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! > >
Description: S/MIME cryptographic signature