John, You're doing the work for the release, so I see it as your call. I've voiced my concern, the release is your baby.
> I've been thinking about this one all morning. When we moved the 2.0.x > stuff in the RC branch up to beta-4, I had some serious reservations > about moving forward with this code. Brett and I (among others, I'm > sure, just don't have the thread at hand ATM) had some heated discussion > about it, and as a result I took a pretty hard look at the code that > went into beta-4...at the time, to find ammunition, but it didn't work > out that way. :-) > > What I saw was a large new body of tests to cover fixed features. When I > upgraded the RC branch again to use beta-4, I found I had little trouble > working around the one issue I did find (which wasn't serious in any > case, and which Brett had handled correctly in code I was trying to hack > back in in a half-assed way). Brett found a second issue, and we worked > around that too with minimal discomfort. > > In absolute terms, I'd say you're right that major new implementations > shouldn't come out in beta releases, or even revisions (like we've done > in Maven itself in the past). However, looking at the issue list you > posted, there are some *very* important fixes in there that IMO would > make going back to beta-2 throwing the baby out with the bathwater. I > *think* it's worth the risk of going with beta-4 for the next release, > and up to this point we've had several discussions about it, without any > absolute vetoes. > > We're in this deep; I'd personally rather risk it knowing we have decent > test coverage in wagon now, and understanding that for every bug we find > we've fixed the use cases for hundreds of other users. > > Just my $0.02 > > -john > > Jason van Zyl wrote: >> Hi, >> >> Wagon changed to much after the beta-3 for my taste and we're pretty >> much in the same boat as we are with Maven 2.0.x versus 2.1.x. >> >> I would like to take the 1.0-beta-3 tag and branch it for Wagon 1.0.x, >> and then make trunk Wagon 1.1.x. >> >> I personally want to stabilize trunk for a release and I want to use >> Wagon beta-3 with some fixes. >> >> I think that 2.0.x should use this Wagon 1.0.x that I would like to make >> from the current beta-3 tag, and 2.1.x can start using some of the new >> Wagon changes. But too much was changed in a beta in Wagon. >> >> Any objections? >> >> Thanks, >> >> Jason >> >> ---------------------------------------------------------- >> Jason van Zyl >> Founder, Apache Maven >> jason at sonatype dot com >> ---------------------------------------------------------- >> >> believe nothing, no matter where you read it, >> or who has said it, >> not even if i have said it, >> unless it agrees with your own reason >> and your own common sense. >> >> -- Buddha >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > -- > John Casey > Developer, PMC Member - Apache Maven (http://maven.apache.org) > Blog: http://www.ejlife.net/blogs/buildchimp/ > > --------------------------------------------------------------------- > 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]
