Yup, I think that's the general consensus, though we do need to sift through the various WAGON* jira projects, and determine what existing issues must be fixed for a 1.0 release, I suppose.
In a way, it's not made things simpler to break up the different wagons into separate jira projects...as far as I can tell, they've been developed/released in lock-step so far. -john On 3/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
So are we pretty much agreed that most things Joakim brought up will be slated for 1.1/2.0 and we'll push a release of this out as soon as we can? Jason. On 27 Feb 07, at 5:23 PM 27 Feb 07, John Casey wrote: > Hi, > > I just committed some changes to trunk that should restore backward > compatibility for using older wagons (at least in the vast majority of > cases). It may still break if there is an older version of a wagon > out there > that doesn't extend from AbstractWagon (since the Wagon interface > picked up > like 5 new methods lately). > > Can we start talking about a Wagon 1.0-final release? What do we > need to get > this done? It looks like the current roadmap only shows 3 > outstanding issues > for the next release. Does anyone have plans for finishing those, > and are > they enough to serve as a basis for a final release? > > I'm just trying to figure out what plans there are for this, since > I'd like > to move toward a 2.1-alpha-1 release of maven, and this is going to > be a > prereq. > > Thanks, > > John --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
