Return-Path: Delivered-To: apmail-jcp-open-archive@www.apache.org Received: (qmail 14806 invoked from network); 28 Aug 2009 18:52:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Aug 2009 18:52:20 -0000 Received: (qmail 73616 invoked by uid 500); 28 Aug 2009 18:52:19 -0000 Delivered-To: apmail-jcp-open-archive@apache.org Received: (qmail 73455 invoked by uid 500); 28 Aug 2009 18:52:19 -0000 Mailing-List: contact jcp-open-help@apache.org; run by ezmlm Precedence: bulk Reply-To: jcp-open@apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list jcp-open@apache.org Delivered-To: moderator for jcp-open@apache.org Received: (qmail 69755 invoked by uid 99); 28 Aug 2009 18:48:24 -0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kwsutter@gmail.com designates 209.85.217.225 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=DciZLOiA8fz3bv4rp9k/TyfvYw90Tl+kGwyLGnbD670=; b=lZBpWtoVUa+rW7TYSbAPB1xm4gVL/2TCoRQNh5z34xbg5QnOMv27Ln+BqPnKtNIWQ7 fOxTNqiv31cm20VESyVyuXUbPgtcCbCA0hO61v0F1lG80aNSrKA9fJiqnalP1KqBVEYR vEq4/vre+fDhofzKRFWY89oUejU178mSmmCBU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=e1JmV6GP47hPe4Ra8lKK9MmsZnYAY2+Gj9t/4/yMXzmrrhRwLn3yCO9bIeCOnsGAwX YHFc/xUaaRSa+e0vA25RASvfWBTJ3f+AoSXvs2wUHB48AwObI+qMiKFUDN5WqLvxbx3G RlZHyn+ixRgO14wGV3EGSAQf02CWaX9sJAgTY= MIME-Version: 1.0 Sender: kwsutter@gmail.com In-Reply-To: References: Date: Fri, 28 Aug 2009 13:47:53 -0500 X-Google-Sender-Auth: a57f47a13288bfa9 Message-ID: <89c0c52c0908281147u35225687me1bb3b6bb9abbe19@mail.gmail.com> Subject: Re: NOTICE wording in spec From: Kevin Sutter To: "Geir Magnusson Jr." Cc: jcp-open@apache.org, dwoods@apache.org Content-Type: multipart/alternative; boundary=000e0cd5d15c257d880472381f3a X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd5d15c257d880472381f3a Content-Type: text/plain; charset=ISO-8859-1 Excellent! Let us know when we're "clear"... Thanks! Kevin On Fri, Aug 28, 2009 at 1:26 PM, Geir Magnusson Jr. wrote: > This is a non-issue. We have discussed this with sun separately, and have > established an agreement (that I have to sign and send back - it was > approved by ASF legal) that removes such requirements. > > I'll post it here once I sign it. > > geir > > > On Aug 28, 2009, at 9:58 AM, Kevin Sutter wrote: > > Hi, >> I was requested by Donald to forward this note exchange between Linda >> DeMichiel (JPA spec lead) and myself (JPA expert group member). I was >> trying to get the JPA NOTICES wording loosened up so that we could more >> easily create Milestone Releases in our Apache OpenJPA project. It sounds >> like her hands are tied. After receiving this reply, I did verify that >> the key Java EE 6 specs that are led by Sun do have the same NOTICES >> wording. But, those specs led by other organizations do not. >> >> >> ---------------------------------------------------------------------------------------------------------------------------------------------------------------- >> Kevin Sutter, Java Persistence API (JPA) >> mail: sutter@us.ibm.com, Kevin Sutter/Rochester/IBM >> http://webspherepersistence.blogspot.com/ >> phone: tl-553-3620 (office), 507-253-3620 (office) >> http://openjpa.apache.org/ >> >> ----- Forwarded by Kevin Sutter/Rochester/IBM on 08/28/2009 08:54 AM ----- >> >> From: >> Linda DeMichiel >> To: >> Kevin Sutter/Rochester/IBM@IBMUS >> Date: >> 08/14/2009 12:45 PM >> Subject: >> Re: NOTICE wording in spec >> Sent by: >> Linda.Demichiel@Sun.COM >> >> >> >> Hi Kevin, >> >> I am bound to this wording and cannot change it. >> >> -Linda >> >> >> Kevin Sutter wrote: >> >>> Hi Linda, >>> Not sure if this needs to be addressed by the whole group or just >>> yourself. Feel free to copy the group on the reply, if it's necessary. >>> >>> Since we're looking for a PFD #2 (Thanks!), I'd like to address the >>> >> NOTICE >> >>> wording 2(iii) on page 2 of the spec. It's been causing problems with >>> Apache... >>> >>> Current wording: >>> >>> (iii)includes the following notice: >>> "This is an implementation of an early-draft specification developed >>> >> under >> >>> the Java Community Process >>> (JCP) and is made available for testing and evaluation purposes only. >>> >> The >> >>> code is not compatible with >>> any specification of the JCP." >>> >>> The "..is made available for testing and evaluation purposes only." is >>> what Apache doesn't like. We've been trying to create interim Milestone >>> >> >> releases in Apache for OpenJPA along the lines of OpenJPA-2.0.0-M1 or >>> OpenJPA-2.0.0-M2. But, any release (even a milestone release) has >>> >> certain >> >>> requirements. Apache doesn't differentiate between an alpha, milestone, >>> >> >> or GA release. A release is a release. And, they don't like to have a >>> release labeled as for "test and evaluation purposes only". Makes >>> >> Apache >> >>> sound more like a "toy" than for real production. And, I agree that a >>> milestone release would not be used for production, but that's what we >>> have to deal with. >>> >>> So, I would like to modify the wording as such: >>> >>> (iii)includes the following notice: >>> "This is an implementation of an early-draft specification developed >>> >> under >> >>> the Java Community Process >>> (JCP). The code is not compatible with any specification of the JCP." >>> >>> Doable? Or, are you bound to some certain wording? I looked at >>> BeanValidation and they don't have any wording along these lines. But, >>> maybe that's not a fair comparison... :-) >>> >>> Thanks, >>> Kevin >>> >> >> >> > --000e0cd5d15c257d880472381f3a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Excellent!=A0 Let us know when we're "clear"...=A0 Thanks!
Kevin

On Fri, Aug 28, 2009 at 1:26 P= M, Geir Magnusson Jr. <geir@pobox.com> wrote:
This is a non-iss= ue. =A0We have discussed this with sun separately, and have established an = agreement (that I have to sign and send back - it was approved by ASF legal= ) that removes such requirements.

I'll post it here once I sign it.

geir


On Aug 28, 2009, at 9:58 AM, Kevin Sutter wrote:

Hi,
I was requested by Donald to forward this note exchange between Linda
DeMichiel (JPA spec lead) and myself (JPA expert group member). =A0I was trying to get the JPA NOTICES wording loosened up so that we could more
easily create Milestone Releases in our Apache OpenJPA project. =A0It sound= s
like her hands are tied. =A0After receiving this reply, I did verify that the key Java EE 6 specs that are led by Sun do have the same NOTICES
wording. =A0But, those specs led by other organizations do not.

---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ----------
Kevin Sutter, Java Persistence API (JPA)
mail: =A0 sutter@us.= ibm.com, Kevin Sutter/Rochester/IBM
htt= p://webspherepersistence.blogspot.com/
phone: =A0tl-553-3620 (office), 507-253-3620 (office)
http://openjpa.apa= che.org/

----- Forwarded by Kevin Sutter/Rochester/IBM on 08/28/2009 08:54 AM -----<= br>
From:
Linda DeMichiel <Linda.Demichiel@Sun.COM>
To:
Kevin Sutter/Rochester/IBM@IBMUS
Date:
08/14/2009 12:45 PM
Subject:
Re: NOTICE wording in spec
Sent by:
Linda.Demichiel@Sun.COM



Hi Kevin,

I am bound to this wording and cannot change it.

-Linda


Kevin Sutter wrote:
Hi Linda,
Not sure if this needs to be addressed by the whole group or just
yourself. =A0Feel free to copy the group on the reply, if it's necessar= y.

Since we're looking for a PFD #2 (Thanks!), I'd like to address the=
NOTICE
wording 2(iii) on page 2 of the spec. =A0It's been causing problems wit= h
Apache...

Current wording:

(iii)includes the following notice:
"This is an implementation of an early-draft specification developed
under
the Java Community Process
(JCP) and is made available for testing and evaluation purposes only.
The
code is not compatible with
any specification of the JCP."

The "..is made available for testing and evaluation purposes only.&quo= t; is
what Apache doesn't like. =A0We've been trying to create interim Mi= lestone

releases in Apache for OpenJPA along the lines of OpenJPA-2.0.0-M1 or
OpenJPA-2.0.0-M2. =A0But, any release (even a milestone release) has
certain
requirements. =A0Apache doesn't differentiate between an alpha, milesto= ne,

or GA release. =A0A release is a release. =A0And, they don't like to ha= ve a
release labeled as for "test and evaluation purposes only". =A0Ma= kes
Apache
sound more like a "toy" than for real production. =A0And, I agree= that a
milestone release would not be used for production, but that's what we<= br> have to deal with.

So, I would like to modify the wording as such:

(iii)includes the following notice:
"This is an implementation of an early-draft specification developed
under
the Java Community Process
(JCP). The code is not compatible with any specification of the JCP."<= br>
Doable? =A0Or, are you bound to some certain wording? =A0I looked at
BeanValidation and they don't have any wording along these lines. =A0Bu= t,
maybe that's not a fair comparison... =A0:-)

Thanks,
Kevin




--000e0cd5d15c257d880472381f3a--