> I'm a little nervous about OpenJPA-222. From talking with > Dave it sounds like it has a large effect on DB2. I'd like to > get that issue resolved if possible.
I'm a little nervous about scope creep. Is there some good reason why OPENJPA-222 needs to be resolved now vs. later? -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: Michael Dick [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 18, 2007 2:24 PM > To: open-jpa-dev@incubator.apache.org > Subject: Re: [VOTE] publish openjpa 0.9.7-incubating release > > On 4/18/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote: > > > > Michael- > > > > On Apr 18, 2007, at 12:27 PM, Michael Dick wrote: > > > > > I'd rather not cut another release, but I think we do need to > > > resolve the issue with the docbook jar. If we can live with the > > > extra jar then the vote can proceed. > > > > Personally, I think it is sufficiently ugly to release with the > > docbook jar to justify starting another release. > > However, if others disagree, I'll happily accede to the majority. For > > now, my vote changes to +0. > > > > > > I agree but like you I can be talked out of it. I'll take > another look > over everything and start another release tonight / tomorrow. > > I'm a little nervous about OpenJPA-222. From talking with > Dave it sounds like it has a large effect on DB2. I'd like to > get that issue resolved if possible. > > > -- > -Michael Dick > 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.
