I'll avoid the >athon and just reply at the top. +1 on git and github. That's more-or-less the lingua franca of open-source now-a-days. Being able to accept pull requests would be awesome! Once it's there, I've got a heap ton of pull requests I'd love to hand off. To that end, we should consider a <git> task in NAnt, and consider moving <cvs> to NAntContrib. I'd like to see <nunit2> either get to 2.5.10 or spun off as a separate project. I had to resort to <exec> to get 2.5.10 working as well. Many SF patches / posts have upgraded the task throughout the years, but it's never gotten pulled into the trunk. If NAnt's cadence is going to be anywhere near previous precedent, <nunit2> has to move separately to remain relevant. I'd like to also throw in my vote to get <msbuild> moved from NAntContrib to NAnt. The <solution> task hasn't worked for me in 5 years, and thus <msbuild> has really become an essential part of NAnt. (Towards the goals of NAnt 2.5, we could shim <solution> to use <msbuild> for VS 2005+ projects/solutions.) Tangentially related, if we used the <msbuild> task to build NAnt, we could easily get "Any CPU" mode -- a result not currently available in the NAnt release package. +1 on moving to .net 2 and generics, and a standard #define net_4 release would also be awesome.
How can I help? Rob ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
