This is a vote to release CXF 2.0.1-incubator.   (attempt #3)

Robert Burrell Donkin found a "legal" issue on the incubator list so I 
had to rebuild the distribution.   Basically, since we include WSS4J, 
BouncyCastle, and XML Security stuff, we have to meet requirements for 
exports around cryptography software.   If you are interested, see:
http://www.apache.org/dev/crypto.html
ALL I've changed is I added the required export notice to the README.   
NOTHING was rebuilt except for the zips/tar.gz's of the distributions.

We still have to update the Apache exports page at:
http://www.apache.org/licenses/exports/
before the official release.  Jim Jagielski has volunteered to help with 
that as it requires site karma which few of us have.   However, I'd like 
to get the vote started on the code itself while that process is 
finished.


There have been a LOT of bug fixes and enhancements in this release 
compared to the 2.0 release.   Many fixes are directly a result of bug 
reports and requests from users that are trying to use the 2.0 release 
and we should try and get them these fixes as quickly as possible.

The two main areas of bug fixes are:
1)  XFire migration (including Aegis databinding usage)

2)  Code first scenarios - services and clients with no WSDL.

However, there are a lot of improvements all over the place with over 60 
Jira tasks/bugs completed:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12312401&styleName=Html&projectId=12310511&Create=Create

The staging area is at:
http://people.apache.org/~dkulp/stage_cxf/2.0.1-incubator_take3/ 

The distributions are in the "dist" directory.
The "maven_repo" directory contains the stuff that will by pushed 
to the m2-incubating-repository.

This release is tagged at:
http://svn.apache.org/repos/asf/incubator/cxf/tags/cxf-2.0.1-incubator/


Here is my +1. (conditional to the exports page update)   The vote will 
be open here for 72 hours.


-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194
[EMAIL PROTECTED]
http://www.dankulp.com/blog

Reply via email to