Since the *NAnt* snapshots have not changed since 2002-11-15, we could use that version as a baseline for testing.
When using workaround [1] for NUnit 2 support, it should be a useful candidate for testing.
[1] http://www.mail-archive.com/nant-users%40lists.sourceforge.net/msg00120.html
The QA snapshot would be most useful if a specific NAntContrib version was also compiled with it.
This would allow various people to test with the same baselined versions.
Once a version is available, we also should be tracking the bugs.
The SourceForge trackers, while not perfect, are better than a mailing list archive to remind us of unsolved problems.
Best regards,
Bernard
Shaw, Gerry wrote:
Placing the responsibility of getting a release out on the project admins isn't going to work if the past is any indication of the future :)The best way to get a release done is for a number of people to take a nant-snapshot and QA it to the level that they would feel comfortable to say that this is a stable release that will add value to users. Needlesss to say you should agree on the date of the snapshot. Once that is done I'm sure one of us can go through the painful process of trying to convince SourceForge to post a release. ------------------------------------------------------- This SF.net email is sponsored by: The Sourceforge Network Survey Take Our Survey and You Could Win a $500 Gift Certificate! http://ugamsolutions.com/psurvey/osdn/SourceForge/index_sourceforge.htm _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
