On Tue, Jul 1, 2008 at 10:27 PM, Nicolas Lalevée <[EMAIL PROTECTED]> wrote:
> > Le 25 juin 08 à 13:24, Xavier Hanin a écrit : > > Hi, >> >> Following the discussion we had already in April or May, I've reviewed all >> issues targeted at 2.0, postponed some of them, and target others to >> 2.0-RC1 >> so that we can more clearly see what we need to do before releasing >> 2.0-RC1. >> ATM there are 29 open issues targeted at RC1, feel free to discuss my >> choices here. >> > > I have done a little review, I didn't spotted anything weird. Allright, thanks! > > > I just saw that strangely tagged issue: IVY-552. I think we should tag it > fixed by IVY-399 As I said in my comment I only left it open with a clear title to let people using 1.4.x find it more easily. But this issue won't ever be fixed in an official Ivy release, since Ivy 1.x is not maintained at ASF, and Jayasoft won't ever release a new Ivy version. So I think we can tag it as resolved / won't fix (because the title targets Ivy 1.4.x only). Xavier > > > >> >> I'll try to spend time this afternoon to get some of those 29 issues >> fixed. >> I still think we really need to get a 2.0 final as soon as possible, some >> of >> the remaining issues are easy to fix, some may take a little longer, but >> with a good community effort we should be able to be done within a >> reasonable timeframe and enjoy a successful 2.0 version! >> > > +1 ! > > Nicolas > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/
