On Fri, 11 May 2007, Steve Loughran <[EMAIL PROTECTED]> wrote: >> http://issues.apache.org/bugzilla/show_bug.cgi?id=42222 > > I can see this is a serious issue; if you follow the links its > causing problems with eclipse 3.3 apps > > options > 1. let Eclipse backport it themselves. > -no work for us, but we end up splitting bug reps between the two > teams, and there's still some issues with the locator stability to > deal with.
I understand Darin to say they've found a work-around without modifying Ant itself. So we probably don't need to rush anything. > 2. rush out an ant1.7.0.1 without adequate testing we could branch from the 1.7.0 tag and just apply that single fix. I wouldn't call that inadeqate testing. Still, if we don't need to push something out that quickly, there is no reason to do that. > 3. Do an Ant1.7.1 with no features, just the current code with tests > all working, including stuff for the locator. > -gets the jscp patch into the field > -gets autoproxy working > -any other minor fixes that have surfaced since ant1.7.0 > > we could still run a tight schedule, but with a single beta > -any other critical fixes to go in? > -cut a beta release for june > -ship in july > > If you look at what I've been putting in the wiki for Ant1.7.1, > there's a mixture of feature creep and packaging; most major > ant1.7.0 defects have been identified already and should be patched. > > We could move all features until Ant1.7.2, make the 1.7.1 the > simpler bugfix release, with less trauma all round. Sounds OK. If we really intend to add new major features, we should call it 1.8 anyway. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
