IANAL, but I have some experience with TCKs.You should be fine with releasing CXF as long as you don't claim compliance with a JSR whose TCK you don't pass. You would want to carefully review the documentation to make the non-compliance clear wherever the relevant JSRs are mentioned.
So your plan sounds fine. Craig On Mar 13, 2007, at 1:14 AM, Bozhong Lin wrote:
Hi,Apache CXF team is planning for its 2.0 final release. In benefit of CXF users, we would like to cut 2.0 release sooner without fully passing JAX-WS TCK, and plan to push JAX-WS TCK test into 2.1 release plan. Of course, in CXF 2.0 release note, we will explicitly mention that Apache CXF does NOT claim any JAX-WS compliant yet, like what we did with CXF 2.0 M1 release. Is this plan OK to incubator PPMC from legal standpoint? Any thoughts/ opinion on this would be greatly appreciated.Thanks, Bo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Craig Russell DB PMC, OpenJPA PPMC [EMAIL PROTECTED] http://db.apache.org/jdo
smime.p7s
Description: S/MIME cryptographic signature
