TODO

This page is a work in progress and is subject to change.

Overview

Objective

This page contains a collection of items that we would like to focus on but have yet to be formally added to the current roadmap. Items on this page are subject to change based on conversations with the developers and the community. We would like to keep this page up-to-date as much as possible going forward.

Current items under discussion

High Priority Items
Topic	Description	Decision
Move away from CVS repository	Sourceforge's repository options seem limited, including types and abilities. I think it would be best to move the source to a new place better suited for code maintenance, storage, and reviewing. No other plans of moving any other services at this time. Two places seem the most appropriate at this time Github and Bitbucket The existing CVS repo will still remain for historical purposes but set to readonly to avoid confusion. The possibility of using SF as a mirror site is still an option depending on the overall decision of this item.	Github.com
Drop .NET/Mono 1.* runtime support	Mainstream support for .NET 1.* has already ended.[9] Target support for 1.* will remain for the time being	OK
Update sln/csproj files to VS.NET 2010	VS.NET 2003 formatted sln/csproj files do not seem to be supported anymore in current available .NET/Mono IDEs	OK
Update <nunit2> task to use NUnit 2.5.10 (or whatever is latest)	High requested item by users NUnit 2.5.10 should support both .NET and Mono frameworks now No need for multiple versions of NUnit for each framework	TBD
Add support for client profile frameworks	They could be net-3.5-cp and net-4.0-cp (or along that line) Should support both target and runtime frameworks	TBD

Medium (Normal) Priority Items
Topic	Description	Decision
Move <trycatch> and <choose> tasks from NAntContrib to NAnt	These two tasks have been identified as mature enough to be imported from NAntContrib to NAnt	TBD
Rework/enhance subversion <svn> tasks in NAntContrib	Improve task quality so they can be ported from NAntContrib to NAnt Possibly use SharpSvn[10] library to help process	TBD
Add Git and Mecurial source control tasks to NAntContrib	Would make sense to add these tasks as these dvcs systems are currently popular Possibly use libgit2sharp[11] and mercurial.net[12] libaries to help process	TBD
Look into NMake replacement	NMake is old and does not seem to be active anymore Possible replacement could be a batch or PowerShell script	TBD
Look into NDoc replacement	NDoc has not been maintained in years and has issues with .net 4.0 (workaround for NAnt is currently in place) NDoc3, Sandcastle, and monodoc could be viable options	TBD
Add a sandcastle task to NAntContrib	Would probably require work on NAntContrib's <msbuild> task	TBD
Add equivalent to Ant's <mapper> type[13]	Requested by users and team members	TBD
Add equivalent to Ant's <macrodef> type[14]	Requested by users	TBD
Add simplified syntax to <move> task to move directories. Like Ant's <move> task.[15]	NAnt's <move> task does move directories using <fileset> Ant can use the following syntax to achieve directory moves: <move file="src/dir" tofile="new/dir/to/move/to"/>	TBD
Colored console output	Have the console output colored text based on the message type Green for successful messages Yellow for warning messages Red for error messages	TBD
Move cvs task from NAnt to NAntContrib	Move the task to NAntContrib until we can improve on its design.	TBD

Low (Nice To Have) Priority Items
Topic	Description	Decision
Website updates	It would be nice to revamp the website layout with an updated look and feel	TBD
Logo update	Like the website, the logo could use a face lift as well. Not sure where original logo came from or what rights the NAnt project has in using it.	TBD
Look into building NAnt plugins	Monodevelop VS.NET Through Nuget?	TBD
Improve commandline argument handling	Look into better ways to handle and format NAnt's console arguments. Mono.Options[16] may help with this.	TBD
Improve NAnt.exe.config formatting	NAnt.exe.config has become a bit overwhelming to maintain. It would be great to find a better way to improve how this is organized so it can be easier to maintain.	TBD
Move to Apache or BSD type license	Was on original release plan on NAnt's website[17] Not sure of feasability Is effort to converting license worth it right now?	TBD