Good to hear Tomas. I would agree with you but I expect that we will have more NAntContrib releases than NAnt releases. Once we get to a 1.0 NAnt release we may not have another NAnt release for a long time. At that point I would expect that most changes will come from new tasks, not changes to the core.
I'm happy to word it anyway you want. From the users point (the devs using NAnt) of view all they should have to do is download NAnt/NAntContrib bundles. We will distribute them so there is no confusion or installation problem. > -----Original Message----- > From: Tomas Restrepo > Subject: Re: [nant-dev] 0.8.0.0 Release > > Hi Scott, > > > I've done a release build for testing purposes. Please try this out > > tonight if you have any time, > > http://nant.sourceforge.net/nant-src-0.8.zip > > Looks good to me. Seems to work just fine here.... I just used it to > recompile several of my projects with no problems at all (including the > one that has about 10 different buildfiles) > > > After this release goes out we will do a NAntContrib release too. Unless > > anyone has any objections NAntContrib releases will include, and depend > > on a specific, NAnt release. > > I'm all for that. The only question is: shouldn't it be the other way > around? That is, shouldn't a NAnt release include a corresponding > NAntContrib release? ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
