Re: Next NAnt/NAntContrib TODO Tasks

I'll avoid the >athon and just reply at the top.
=A0
+1 on git and github.=A0 That's more-or-less the lingua franca of open-sour=
ce=A0now-a-days.=A0 Being able to accept pull
requests would be awesome!=A0 Once it's
there, I've got a heap ton of pull requests I'd love to hand off.=A0 To tha=
t end, we should consider a <git>
task in NAnt, and consider moving <cvs> to NAntContrib.
=A0
I'd like to see <nunit2>
either get to 2.5.10 or spun off as a separate project.=A0 I had to resort =
to <exec> to get 2.5.10
working as well.=A0 Many SF patches / posts
have upgraded the task throughout the years, but it's never gotten pulled i=
nto the trunk.=A0 If NAnt's cadence is going to be anywhere
near previous precedent, <nunit2> has to move separately to remain relevant.
=A0
I'd like to also throw in my
vote to get <msbuild> moved from NAntContrib to NAnt.=A0 The <solution> tas=
k hasn't worked for
me in 5 years, and thus <msbuild> has really become an essential part of
NAnt. =A0(Towards the goals of NAnt 2.5, we could shim <solution> to use <m=
sbuild> for VS 2005+ projects/solutions.)=A0=A0Tangentially 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.
=A0
+1 on moving to .net 2 and
generics, and a standard #define net_4 release would also be awesome.

How can I help?
=A0
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