You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by Kevan Miller <ke...@gmail.com> on 2010/04/02 23:31:33 UTC
Re: Wink 1.1 release progress
On Mar 30, 2010, at 10:22 PM, Mike Rheinheimer wrote:
> Next up, ideally, I'd like to have someone run the 1.1 TCK to confirm
> we are still fully compliant. Who can volunteer for this?
> Unfortunately, I cannot.
Here's general information about getting access to TCK materials. See http://apache.org/jcp/#gettingtck for more information.
You'd need to fill out the ASF Non-Disclosure Agreement -- http://apache.org/jcp/ApacheNDA.pdf
You can then request access to the JAX-WS TCK by sending a note to jcp-open@apache.org.
Some projects manage TCK materials within the project (e.g. Geronimo). This isn't a requirement. For technology projects like Wink with relatively small TCKS, a committer can send a note to jcp-open@apache.org (after they've submitted their NDA) and request the JAX-WS TCK materials. Typically, the TCK is placed in your home directory on people.apache.org.
You are expected to keep TCK materials private. Also, some care needs to be taken in publicly discussing the TCK.
--kevan
Re: Wink 1.1 release progress
Posted by Mike Rheinheimer <ro...@ohmyhead.com>.
Fair points. Regardless of the ability or inability to stay in step
with the JAX-RS spec version, we might appear to the casual observer
to be going backward in function based on the lack of TCK compliance
declarations.
Poeple may read the Wink 1.0 release notes, seeing the JAX-RS 1.0
compliance statement, then get Wink 1.1 release notes, and see no such
claims. Wouldn't this discourage putting it into production as well?
I'm not emotionally attached to keeping Wink version numbers in sync
with spec version numbers, but it does concern me that we would make
an official release that, at first glance, appears to be less
compliant than previous releases based on the lack of TCK runs.
Maybe ASF needs a "compliance" team. :)
mike
On Fri, Apr 16, 2010 at 12:07 PM, Davanum Srinivas <da...@gmail.com> wrote:
> Mike,
>
> beta discourages folks from putting things into production. As to
> label wink 1.1 being compliant with jaxrs 1.1 spec version, this is
> going to be a one time deal jaxrs spec is going to be updated on its
> own schedule and frankly i don't know if anyone is even discussing a
> 1.2 version. So i am not a fan of lock step with tck version.
>
> If everyone here think it's ready, then it's ready. Whether TCK
> compliant or not. If it's ready, then it should get its own version #
> and not be called beta. If it's not ready, then we need to figure out
> what would make it ready (other than TCK compliance)...
>
> my 2 cents and my VOTE is to go with 1.1 release
>
> -- dims
>
> On Fri, Apr 16, 2010 at 11:30 AM, Mike Rheinheimer <ro...@ohmyhead.com> wrote:
>> Winkers,
>>
>> Since I've had no takers on my call for volunteers to run the JAX-RS
>> 1.1 TCK against the latest Wink trunk, I think we can and should move
>> forward with a release without it. However...
>>
>> Without any JAX-RS TCK runs, whether 1.0 or 1.1 against a new Wink
>> release, we CANNOT claim compliance with any version of the
>> specification. Remember this as we consider a release. The Apache
>> Wink 1.0-incubating release contains this statement in the release
>> notes: "Apache Wink is TCK compliant implementation of the JAX-RS
>> v1.0 specification." Considering that no JAX-RS TCK will have been
>> executed against the proposed upcoming release, Wink will not be able
>> to claim any compliance, even to JAX-RS 1.0.
>>
>> Given this information, and the prior stated desire to have the Wink
>> release number align with the JAX-RS specification version it
>> implements, do we want to:
>>
>> 1) release Apache Wink as a 1.1-beta (incubating), so as to preserve
>> the 1.1 version number for a TCK-certified future release?
>>
>> 2) release Apache Wink as 1.1 (incubating), thereby removing the
>> possibility of aligning Wink version numbers with the JAX-RS
>> specification it implements?
>>
>> There is no special restrictions placed on releasing a "beta". That
>> is simply a naming convention used by an Apache project to clearly
>> indicate the intent and functionality claims around that particular
>> release. (Example:
>> http://repo2.maven.org/maven2/org/apache/myfaces/core/myfaces-core-project/)
>>
>> My opinion: go ahead with the release process, and use option (1). I
>> think this is best, given that we will appear to be going "backward"
>> in capability due to the inability to claim TCK compliance.
>>
>> Remember, execution of the JAX-RS 1.1 TCK against Wink trunk, then
>> again on the branch that would be created resolves this problem!
>> Whomever volunteers to run the TCK will be rewarded with unimaginable
>> satisfaction! Ok, maybe not, but you'll get a big thank you. :)
>>
>> mike
>>
>>
>>
>> On Fri, Apr 2, 2010 at 4:31 PM, Kevan Miller <ke...@gmail.com> wrote:
>>>
>>> On Mar 30, 2010, at 10:22 PM, Mike Rheinheimer wrote:
>>>
>>>> Next up, ideally, I'd like to have someone run the 1.1 TCK to confirm
>>>> we are still fully compliant. Who can volunteer for this?
>>>> Unfortunately, I cannot.
>>>
>>>
>>> Here's general information about getting access to TCK materials. See http://apache.org/jcp/#gettingtck for more information.
>>>
>>> You'd need to fill out the ASF Non-Disclosure Agreement -- http://apache.org/jcp/ApacheNDA.pdf
>>>
>>> You can then request access to the JAX-WS TCK by sending a note to jcp-open@apache.org.
>>>
>>> Some projects manage TCK materials within the project (e.g. Geronimo). This isn't a requirement. For technology projects like Wink with relatively small TCKS, a committer can send a note to jcp-open@apache.org (after they've submitted their NDA) and request the JAX-WS TCK materials. Typically, the TCK is placed in your home directory on people.apache.org.
>>>
>>> You are expected to keep TCK materials private. Also, some care needs to be taken in publicly discussing the TCK.
>>>
>>> --kevan
>>
>
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
Re: Wink 1.1 release progress
Posted by Davanum Srinivas <da...@gmail.com>.
Mike,
beta discourages folks from putting things into production. As to
label wink 1.1 being compliant with jaxrs 1.1 spec version, this is
going to be a one time deal jaxrs spec is going to be updated on its
own schedule and frankly i don't know if anyone is even discussing a
1.2 version. So i am not a fan of lock step with tck version.
If everyone here think it's ready, then it's ready. Whether TCK
compliant or not. If it's ready, then it should get its own version #
and not be called beta. If it's not ready, then we need to figure out
what would make it ready (other than TCK compliance)...
my 2 cents and my VOTE is to go with 1.1 release
-- dims
On Fri, Apr 16, 2010 at 11:30 AM, Mike Rheinheimer <ro...@ohmyhead.com> wrote:
> Winkers,
>
> Since I've had no takers on my call for volunteers to run the JAX-RS
> 1.1 TCK against the latest Wink trunk, I think we can and should move
> forward with a release without it. However...
>
> Without any JAX-RS TCK runs, whether 1.0 or 1.1 against a new Wink
> release, we CANNOT claim compliance with any version of the
> specification. Remember this as we consider a release. The Apache
> Wink 1.0-incubating release contains this statement in the release
> notes: "Apache Wink is TCK compliant implementation of the JAX-RS
> v1.0 specification." Considering that no JAX-RS TCK will have been
> executed against the proposed upcoming release, Wink will not be able
> to claim any compliance, even to JAX-RS 1.0.
>
> Given this information, and the prior stated desire to have the Wink
> release number align with the JAX-RS specification version it
> implements, do we want to:
>
> 1) release Apache Wink as a 1.1-beta (incubating), so as to preserve
> the 1.1 version number for a TCK-certified future release?
>
> 2) release Apache Wink as 1.1 (incubating), thereby removing the
> possibility of aligning Wink version numbers with the JAX-RS
> specification it implements?
>
> There is no special restrictions placed on releasing a "beta". That
> is simply a naming convention used by an Apache project to clearly
> indicate the intent and functionality claims around that particular
> release. (Example:
> http://repo2.maven.org/maven2/org/apache/myfaces/core/myfaces-core-project/)
>
> My opinion: go ahead with the release process, and use option (1). I
> think this is best, given that we will appear to be going "backward"
> in capability due to the inability to claim TCK compliance.
>
> Remember, execution of the JAX-RS 1.1 TCK against Wink trunk, then
> again on the branch that would be created resolves this problem!
> Whomever volunteers to run the TCK will be rewarded with unimaginable
> satisfaction! Ok, maybe not, but you'll get a big thank you. :)
>
> mike
>
>
>
> On Fri, Apr 2, 2010 at 4:31 PM, Kevan Miller <ke...@gmail.com> wrote:
>>
>> On Mar 30, 2010, at 10:22 PM, Mike Rheinheimer wrote:
>>
>>> Next up, ideally, I'd like to have someone run the 1.1 TCK to confirm
>>> we are still fully compliant. Who can volunteer for this?
>>> Unfortunately, I cannot.
>>
>>
>> Here's general information about getting access to TCK materials. See http://apache.org/jcp/#gettingtck for more information.
>>
>> You'd need to fill out the ASF Non-Disclosure Agreement -- http://apache.org/jcp/ApacheNDA.pdf
>>
>> You can then request access to the JAX-WS TCK by sending a note to jcp-open@apache.org.
>>
>> Some projects manage TCK materials within the project (e.g. Geronimo). This isn't a requirement. For technology projects like Wink with relatively small TCKS, a committer can send a note to jcp-open@apache.org (after they've submitted their NDA) and request the JAX-WS TCK materials. Typically, the TCK is placed in your home directory on people.apache.org.
>>
>> You are expected to keep TCK materials private. Also, some care needs to be taken in publicly discussing the TCK.
>>
>> --kevan
>
--
Davanum Srinivas :: http://davanum.wordpress.com
Re: Wink 1.1 release progress
Posted by Mike Rheinheimer <ro...@ohmyhead.com>.
Winkers,
Since I've had no takers on my call for volunteers to run the JAX-RS
1.1 TCK against the latest Wink trunk, I think we can and should move
forward with a release without it. However...
Without any JAX-RS TCK runs, whether 1.0 or 1.1 against a new Wink
release, we CANNOT claim compliance with any version of the
specification. Remember this as we consider a release. The Apache
Wink 1.0-incubating release contains this statement in the release
notes: "Apache Wink is TCK compliant implementation of the JAX-RS
v1.0 specification." Considering that no JAX-RS TCK will have been
executed against the proposed upcoming release, Wink will not be able
to claim any compliance, even to JAX-RS 1.0.
Given this information, and the prior stated desire to have the Wink
release number align with the JAX-RS specification version it
implements, do we want to:
1) release Apache Wink as a 1.1-beta (incubating), so as to preserve
the 1.1 version number for a TCK-certified future release?
2) release Apache Wink as 1.1 (incubating), thereby removing the
possibility of aligning Wink version numbers with the JAX-RS
specification it implements?
There is no special restrictions placed on releasing a "beta". That
is simply a naming convention used by an Apache project to clearly
indicate the intent and functionality claims around that particular
release. (Example:
http://repo2.maven.org/maven2/org/apache/myfaces/core/myfaces-core-project/)
My opinion: go ahead with the release process, and use option (1). I
think this is best, given that we will appear to be going "backward"
in capability due to the inability to claim TCK compliance.
Remember, execution of the JAX-RS 1.1 TCK against Wink trunk, then
again on the branch that would be created resolves this problem!
Whomever volunteers to run the TCK will be rewarded with unimaginable
satisfaction! Ok, maybe not, but you'll get a big thank you. :)
mike
On Fri, Apr 2, 2010 at 4:31 PM, Kevan Miller <ke...@gmail.com> wrote:
>
> On Mar 30, 2010, at 10:22 PM, Mike Rheinheimer wrote:
>
>> Next up, ideally, I'd like to have someone run the 1.1 TCK to confirm
>> we are still fully compliant. Who can volunteer for this?
>> Unfortunately, I cannot.
>
>
> Here's general information about getting access to TCK materials. See http://apache.org/jcp/#gettingtck for more information.
>
> You'd need to fill out the ASF Non-Disclosure Agreement -- http://apache.org/jcp/ApacheNDA.pdf
>
> You can then request access to the JAX-WS TCK by sending a note to jcp-open@apache.org.
>
> Some projects manage TCK materials within the project (e.g. Geronimo). This isn't a requirement. For technology projects like Wink with relatively small TCKS, a committer can send a note to jcp-open@apache.org (after they've submitted their NDA) and request the JAX-WS TCK materials. Typically, the TCK is placed in your home directory on people.apache.org.
>
> You are expected to keep TCK materials private. Also, some care needs to be taken in publicly discussing the TCK.
>
> --kevan