Hi Ryan, +1 for github.
And we should define/discus a contribution process to ensure that nant core will stay as stable as it is currently. Other proposals: - Color output. Red for errors, yellow for warning and green for sucessfull build. I added this to my own net_2.0 build and I'm addicted to this easily identifying Green successfull build message. - solution task/msbuild polishing since there still issues with our projects. SourceControl: - move CVS to nantcontrib - integrate git - polish svn - add tfs (see ci-factory) http://ci-factory.googlecode.com/svn/Current/Product/Production/Nant/TF.Tasks/ lower priority: - review nant.exe.config: maybe separate net-x and mono-x definitions or one for each target. It is very large and hardly to maintain. - fix/polish commandline handling: - remove anoying ":" as separator, this prevents you from using tab completion in cmd window (even WiX did this with 3.5 release) - add double dash as parameter prefix (as used at gnu tools) at least for --help and --version Check other ci-factory tasks to add them to nantcontrib. Hint: I found macrodef at ci-factory: http://ci-factory.googlecode.com/svn/Current/Product/Production/Nant/CIFactory.NAnt.Tasks/Tasks/ It was getting longer and longer. So far Dominik -- The answer to the great question of life, the universe and everything is 42 (Douglas Adams) ------------------------------------------------------------------------------ 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
