If I do that, we'll have to redo this vote. I'm hoping to get 2.2.1 out
to fix some problems in 2.2.0 that make it nearly unusable for deployment.
Is this issue important enough to push the release off by another week?
If not, can we just push it out as part of 2.2.2 or 2.3.0 or whatever
$NEXT is?
-john
Vincent Siveton wrote:
+1
But I hope that you will bump to latest modello to fix MNG-4289.
Cheers,
Vincent
2009/8/6, John Casey <[email protected]>:
Hi,
It looks like we've got a stable release candidate that addresses the major
regressions that resulted from the Maven 2.2.0 release.
The artifacts we're voting on for the 2.2.1 release are here:
https://repository.apache.org/content/repositories/maven-staging-018/
The distribution artifacts are here:
https://repository.apache.org/content/repositories/maven-staging-018/org/apache/maven/apache-maven/2.2.1/
We've resolved 14 issues for this release:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=15328
Let's give this vote 72h and see how it goes.
+1/+0/-1
Here's my +1.
Thanks,
-john
---
John Casey
Developer and PMC Member, Apache Maven (http://maven.apache.org)
Member, Apache Software Foundation
"What we have to learn to do, we learn by doing."
-Aristotle
---------------------------------------------------------------------
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]
