Following up on Arnaud's comments:
In principle I agree with the 'release early, release often' philosophy
- as long as there is something to release. Looking at the Jira roadmap
[1] most of the closed Jira's for m11b3 are documentation issues and a
few trivial fixes. Functionally, the current core is completely
equivalent to the one in m11b2.
The only big change that has ocurred IMO is that Arnaud has unified
practically all dependencies used in the core and the core plugins [2]
which has solved quite a few consistency issues. However, releasing a
new distribution now would only make sense if all the included plugins
would use the same set of dependencies. That's why we are working on
re-releasing the plugins first.
Finally, as Jeff has pointed out, I am also not happy about the naming,
I think m11b2 and the current m11b3-SNAPSHOT are far superior and more
stable than the suffix 'beta' would suggest.
And again: any help would be very welcome! :)
-Lukas
[1]
http://jira.codehaus.org/browse/MAVEN?report=com.atlassian.jira.plugin.system.project:roadmap-panel
[2]
http://maven.apache.org/maven-1.x/plugins/bundled/dependency-convergence-report.html
Arnaud HERITIER wrote:
Hi all,
We (the few m1.1 developpers) are completly agree with you.
Release early, release often is what we are trying to do for plugins
because you can use them today in maven 1.0.2 or in maven 1.1 beta X.
In the history page [1] and in our you can see that we are releasing a lot
of plugins since maven 1.1 beta 2 ( I don't talk about maven 1.0.2 ).
For the main distribution the problem is more complex.
We have actually a lot of blocking bugs (multiproject problems, xml
entities not supported, ...) that we have to fix before to release maven
1.1-beta-3 :
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&type=1&pid=10030&status=1&status=3&status=4
But these bugs are also depending of external libraries (jelly, dom4j,
jaxen, ....) and some of these projects are a little bit dead. It's why
maven 2 uses less external dependencies to not reproduce this error.
And the last point : The community for m1 is less and less active. People
are migrating to maven 2 and nobody wants to lost his time to debug and
patch maven 1.1 :-(
Cheers
Arnaud
[1] http://maven.apache.org/maven-1.x/plugins/bundledHistory.html
[2]
http://docs.codehaus.org/display/MAVEN/Maven+1.1+plugins<http://docs.codehaus.org/display/MAVEN/Maven+1.1+plugins>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
