ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Darin Swanson <Darin_Swan...@us.ibm.com>
Subject Re: ant 1.7.1
Date Sat, 12 May 2007 00:03:34 GMT
Thank you for the fast response.

I have released a workaround within the Eclipse 3.3 code base.
Please see  https://bugs.eclipse.org/bugs/show_bug.cgi?id=183283 for the 
details.
We could still have problems but I believe the critical paths are now 
covered.

So currently my vote would be #3 (if you are looking for non-committer 
input :-) )

Thanks again
Darins




Steve Loughran <stevel@apache.org> 
05/11/2007 02:12 PM
Please respond to
"Ant Developers List" <dev@ant.apache.org>


To
Ant Developers List <dev@ant.apache.org>
cc

Subject
ant 1.7.1






bugzilla@apache.org wrote:
> DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
> RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
> <http://issues.apache.org/bugzilla/show_bug.cgi?id=42222>.
> ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
> INSERTED IN THE BUG DATABASE.
> 
> 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.

2. rush out an ant1.7.0.1 without adequate testing
  -I dont like this, because I've been in projects before that shipped 
things to meet WebSphere's needs, and it hurt in the end (Axis, BTW). 
Quality gets dropped at the expense of timeliness, but you end up 
getting all the support calls anyway

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.

Thoughts?

-steve



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org



Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message