-1
I would really like to see PLUTO-581 ans PLUTO-569 fixed as part of this
release. Both these bugs provide specific suggestions for code fixes.
Both these bugs have a significantly impair the JSF Bridge from
executing properly in a Pluto 2.0 environment. The second bug causes
JSF based portlets using events to deadlock. The first leads to
situations where submitted parameters are lost because they aren't
properly decoded.
-Mike-
On 4/13/2010 9:14 AM, Ate Douma wrote:
Hi Pluto Team and community,
I've staged a release candidate for the new Pluto 2.0.1 release.
Please review the release candidate for this project which is
available in the following Nexus provided staging repository:
https://repository.apache.org/content/repositories/orgapacheportals-019/
The most important part is the big source archive of Pluto which is here:
https://repository.apache.org/content/repositories/orgapacheportals-019/org/apache/portals/pluto/pluto/2.0.1/
Please also check the various maven artifacts we're deploying to the
global maven repository:
https://repository.apache.org/content/repositories/orgapacheportals-019/org/apache/portals/pluto/
In addition, I'm providing a binary Distribution (Pluto+Tomcat) based
on this release candidate here:
http://people.apache.org/~ate/releases/portals/pluto/
Please vote on releasing Apache Pluto 2.0.1
This vote is open for the next 72 hours.
Please cast your vote:
[ ] +1 for Release
[ ] 0 for Don't care
[ ] -1 Don't release (do provide a reason then)
Regards,
Ate Douma
