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 <[email protected]> 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 > [email protected]. > > 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 [email protected] (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
