Now that Maven 3 beta 3 is out with Guice and Aether, we can pretty safely call it feature complete. I'd like to propose a few goals to get some things done. We have ApacheCon coming up the first week of November, and it would be great to set that as a target to get Maven 3.0 out the door.
So far the feedback on the betas has been good but fairly limited. I think that without a clear plan, and our history with this mammoth release, people are probably reluctant to spend a lot of time testing each beta. In the past we've been successful pushing out release candidate builds and involving the user list. If we start that soonish, there should be plenty of time to uncover and fix regressions, especially if everyone pitches in. There's even time to cut another beta before we launch into the RCs if it's needed. So first of all, Benjamin, Herve, Kristian you've collectively done the majority of the work in M3 recently. Do you think the above is achievable and desirable? What does everyone else think? Secondly, For me personally, I'm going to commit to get the Maven Index code committed and to push updated releases of the dependency and enforcer plugins before ApacheCon. Anyone else want to ante up for some chunk of work and get things rolling? Thanks, Brian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
