On Aug 6, 2010, at 11:22 AM, Brian Fox wrote: > I'm not so concerned about confusing users with a beta2 and then a > beta3, that can be mitigated easily in the announcement. More releases > won't hurt anyone. >
If we were deciding to leave Guice/Aether to Maven 3.1 then my opinion would be let it rip, the more the merrier. For me crux is are we deciding to put this new code into 3.0? If so, we have more betas with the old code then new doesn't make any sense to me. By releasing the trunk now as beta-2 it seems to satisfy the wants of some of the people voting here but ultimately people who adopt these betas in the Maven user base is going to be miniscule. So this beta satisfies the wants of very few people in real terms. It's also a focal point as I see for for people always complaining that Sonatype dominates. If you believe the Guice/Aether code should go into 3.0 then you fully back that plan as a committer and help fix the problems before we release it. In practical terms if no one else helps, it really makes no difference to us to debug the Guice/Aether code. The only thing that might potentially help for Benjamin is if people used the old/new versions to do diffs on behaviour. No normal user is going to do this, any one adept enough to have done this already can do it with a build out of Hudson. I also frankly want to prevent someone from saying after we release the beta-2 that "Oh maybe we should just wait to integrate Guice/Aether until 3.1" at which point we're either stuck holding the bag to maintain a codebase in parallel or we quickly release a 3.1 which would be even more confusing then a beta2/beta3 now. If you support the direction, then let's work together and really if 5 people pull out the debuggers and profilers to help track down the problems we'll likely find them. At the very least it gives committers here the opportunity to learn the code that is the basis of future of Maven. If that happens it might only take into early next week to fix the problems and then we release what we plan to go forward with for the life of Maven 3. If really what people are saying is the we want what we want now, and then just sit back and let us fix all the problems with the Guice/Aether code I'll frankly be disappointed. Really after all the work that has been done thus far what is another week or two? > Let those working on it decide what to do and when presented with a > vote, I'll test, verify and vote accordingly, regardless of if it's > beta2 with or without Aether/Guice. I would just rather see one > sooner rather then later. We too often have a tendency of waiting for > everything to be perfect. They are betas, pick one and stage it I say. I can't block a vote, but i honestly don't think it's a matter of trying to be perfect and more a matter of getting a level of commitment from the developers. And I think it's far too easy to under estimate the confusion it will cause users dropping betas out so closely no matter how much messaging you do in announcements. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --------------------------------------------------------- Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition
