This has been open for more than 72 hours now and the vote has passed.  

There are no -1 votes.

4 binding +1 votes from:
Paul Fremantle
Robert Burrell Donkin
Jim Jagielski
Davanum Srinivas


11 non-binding +1 votes from:
Dan Diephouse
Guillaume Nodet
Jervis Lui
Bozhong Lin
Eoghan Glynn
Tao Li
Willem Jiang
Freeman Fang
James Mao
Jim Ma
Peter Jones

Based on this I am now calling the vote closed, and releasing Apache CXF 
Milestone 1.

A huge thanks to everyone that worked on the release as well as to those that 
looked at it with a legal eye and voted on it.  The entire CXF team really 
appreciates the efforts of everyone involved.

Thanks!
-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194
[EMAIL PROTECTED]



On Tuesday 12 December 2006 23:08, Daniel Kulp wrote:
> Based on conversations with various people, the Apache CXF Team decided to
> change the release notes in RC3 to add a disclaimer about the level of
> support for the JAX-WS API's since no TCK tests have been run.   The ONLY
> change made to the branch was the release_notes.txt file.   However, that
> required rebuilding new distributions, thus a new vote is required.
>
> Binaries and Source Distributions:
> http://people.apache.org/~blin/incubator-cxf-2.0-M1-v4/
> Maven Repository:
> http://people.apache.org/~blin/incubator-cxf-2.0-M1-v4/repository/org/apach
>e/cxf/ Wiki Copy of Release notes:
> http://cwiki.apache.org/confluence/display/CXF/Apache+CXF+2.0-M1+Incubating
>+Release+Notes
>
>
> We ask that you please vote to approve this release:
> [ ] +1 Release the binary as Apache Incubator CXF 2.0-M1
> [ ] -1 Issue detected (please provide details)
>
>
> Thanks for everyone who has helped so far with the previous release
> candidates and this one!
>
> - The CXF team

-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194
[EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to