Hi Thomas,

had a look at it

[X] -1 no, do not release it because


Blockers

+) some signatures are invalid - checkout "gpg --verbose --verify-files *.asc" +) Cobertura did not pick up the regressions test and don't show any test coverage - I think that is caused by a broken Cobertura integration +) the links to the Avalon services are broken on the left side (Documentation/Services/XSLT Service) , e.g. http://turbine.apache.org/builds/turbine/turbine/4.0-M1/fulcrum/fulcrum-xslt/

Nice to have (a bit selfish)

+) commons-email could be pushed to 1.2 since it contains a lot of bug fixes (and 1.1 was broken)
+) at least one contributor is missing ant that could be me .... ;-)

Cheers,

Siegfried Goeschl

PS: And yes - thanks a lot for pushing a Turbine release

On 05.04.11 22:19, Thomas Vandahl wrote:
Hi folks,

I took the liberty to prepare a release candidate for the M1 milestone
release of Turbine 4.0. This milestone release is made for verification
of the newly integrated Fulcrum services and to gather experience (and
documentation) on how to migrate a 2.3.3 installation to the new
architecture.

Please verify this release candidate, especially the completeness of the
source and binary distribution packages and vote...

Tag:

https://svn.apache.org/repos/asf/turbine/core/tags/TURBINE_4_0_M1/

Site:

http://turbine.apache.org/builds/turbine/turbine/4.0-M1/RC1/site/

Source and Binaries:

http://turbine.apache.org/builds/turbine/core/turbine/4.0-M1/RC1/staged/org/apache/turbine/turbine/4.0-M1/


[ ] +1 release it
[ ] +0 go ahead I don't care
[ ] -1 no, do not release it because

Bye, Thomas.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to