Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: open-jpa-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of kwsutter@gmail.com designates
 64.233.166.178 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=umcnOVUX+SDn4cngBS4wg+NAeU/mRw4Q4Ob6eQH2EyKRmkr5COQVdc/chEr7k4mYcltSuhLdcRdYM3epmhOl8BTWPhC356gUIDt0wtvPVX+ROFMLZi1Ge/+0+IVhicx18vXzPwnY3u+4eVj6QmtrEWnD/AU0Ls7JMcTq59Yjc9A=
Message-ID: <89c0c52c0704190752p4a733832qfebc97dc54245949@mail.gmail.com>
Date: Thu, 19 Apr 2007 09:52:29 -0500
From: "Kevin Sutter" <kwsutter@gmail.com>
To: open-jpa-dev@incubator.apache.org
Subject: Re: [VOTE] publish openjpa 0.9.7-incubating release
In-Reply-To: <89c0c52c0704190534w5c84b661w4cb40eba3ffaab9a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_97532_16219514.1176994349129"
References: <72c1350f0704160910s29d0bfddtdd97752c0d44bc82@mail.gmail.com>
	 <e9ac83540704181142j2951f1f5l52c94d95da29c8f2@mail.gmail.com>
	 <3CFEC483-9D69-41F4-88AA-4181DCDF2BEA@SUN.com>
	 <72c1350f0704181227n4474973axd7856bb589924556@mail.gmail.com>
	 <17F360A1-6896-4E20-88ED-D60C153869B5@apache.org>
	 <72c1350f0704181423u6277ae14ya3d3a19ff5c18d38@mail.gmail.com>
	 <7D856CDFE035FF45A0420ACBD71BDD6303F4FA8B@repbex02.amer.bea.com>
	 <72c1350f0704181640i3ce24dbfxe52ab080091feb05@mail.gmail.com>
	 <EAD1EDCF-F7B2-4286-B2F4-750EC598779F@SUN.com>
	 <89c0c52c0704190534w5c84b661w4cb40eba3ffaab9a@mail.gmail.com>

------=_Part_97532_16219514.1176994349129
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Another alternative is to back out the changes for OPENJPA-182 until we get
the complete solution..  But, looking at the changes for OPENJPA-182, that
looks to be quite the job and I'm not sure how many of these parts have been
touched since that commit...  I would rather wait until OPENJPA-222 tests
clean and then go forward with another vote...  But, I am open to other
suggestions.

Kevin

On 4/19/07, Kevin Sutter <kwsutter@gmail.com> wrote:
>
> Craig and others,
> Here's the scoop with OPENJPA-222...  A couple of weeks ago, DaveW
> committed some changes to OPENJPA-182.  Patrick reviewed the changes and
> through discussions on the dev mailing list and the Issue itself, re-worked
> and re-committed the changes.  We dropped the ball and didn't sufficiently
> test these new changes against DB2 until recently.  We are finding that
> basically any sub-selects will not work with DB2 with the changes for
> OPENJPA-182.  The changes for OPENJPA-222 will resolve these issues.
>
> This problem (no sub-selects with DB2) seems severe enough to warrant a
> re-spin of the release.  I know this pushes us out another couple of days,
> but I think from a "customer perspective", it's worth the effort.
>
> As far as this 0.9.7 being bundled with some significant release...  We
> (IBM) were planning to use the 0.9.7 release with a refresh of the EJB3
> Feature Pack.  Our plans have since changed, so the urgency is no longer
> present.  I just want any OpenJPA release to be usable and not regress
> expected function.
>
> Thanks,
> Kevin
>
> On 4/18/07, Craig L Russell <Craig.Russell@sun.com> wrote:
> >
> > This isn't the last release of openjpa. What is the urgency for
> > fixing this before our major event (the last release before exiting
> > the incubator)?
> >
> > Is this release planned to be bundled with some other significant
> > release?
> >
> > Craig
> >
> > On Apr 18, 2007, at 4:40 PM, Michael Dick wrote:
> >
> > > I probably should have worded that differently since I haven't run
> > > the tests
> > > against DB2. I believe Dave's team has.
> > >
> > > Dave, can you comment on how big the impact of OpenJPA-222 is?
> > >
> > > On 4/18/07, Patrick Linskey <plinskey@bea.com> wrote:
> > >>>
> > >>> 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:michael.d.dick@gmail.com ]
> > >> > 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 <mprudhom@apache.org> 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.
> > >>
> > >
> > >
> > >
> > > --
> > > -Michael Dick
> >
> > 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!
> >
> >
> >
>

------=_Part_97532_16219514.1176994349129--