Re: [NMock2-Dev] NMock Cleanup

[Steve M. <Ste...@ty...>]

The first item definitely,  I'd like to get it on a clean slate by
getting stuff related to NMock1 out of the list.

We've had discussion before about moving from CVS into subversion.
Again, this is an area where it really doesn't matter to me,  I've got
both clients loaded so it doesn't really matter.

-----Original Message-----
From: nmo...@li...
[mailto:nmo...@li...] On Behalf Of
aci...@ac...
Sent: Thursday, November 08, 2007 2:39 PM
To: NMock2 Development Discussion
Subject: [NMock2-Dev] NMock Cleanup

I've been thinking about what we need to do to make NMock2 really look
alive again, and while the new RC that should be coming soon will be a
big
boost we need to cleanup SourceForge and the website so that we aren't
showing outdated information.

Proposals:

Close all bugs/Support requests that are not related to NMock2.
Import the current nmock2 directory from CVS into Subversion to get away
from NMock 1.0 legacy code.
Update the SourceForge developer list to reflect current developers
Decide who should have commit access to the code.

There are more ideas floating around in my head and when I can
articulate
them I'll send them on. Discussion on these ideas is welcome and
encouraged.

-Richard Holden


------------------------------------------------------------------------
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NMock-two-dev mailing list
NMo...@li...
https://lists.sourceforge.net/lists/listinfo/nmock-two-dev