Re: [NMock2-Dev] NMock Cleanup

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

We are going to label the trunk before we start making modifications to
remove 1.1 support from the project, so if anyone wants to become the
official 1.1 maintainer, then they can start a branch from that point
and keep the 1.1 code alive.

-----Original Message-----
From: nmo...@li...
[mailto:nmo...@li...] On Behalf Of
Charlie Poole
Sent: Saturday, November 10, 2007 11:15 AM
To: 'NMock2 Development Discussion'
Subject: Re: [NMock2-Dev] NMock Cleanup

Is it definitely decided that you guys won't support 1.1
any longer? If that's true, I think it would be important
to facilitate others continuing to support it.

It would reassure me to see a public statement of direction=20
of some kind that covered what CLRs you will support. I'm
kind of hoping that the support will match what NUnit=20
supports, but I realize you can only do what you can do.

Charlie=20

> -----Original Message-----
> From: nmo...@li...=20
> [mailto:nmo...@li...] On=20
> Behalf Of Steve Mitcham
> Sent: Friday, November 09, 2007 6:17 AM
> To: NMock2 Development Discussion
> Subject: Re: [NMock2-Dev] NMock Cleanup
>=20
> We should also do the work to close off the 1.1 support and=20
> move the solution file forward to 2005 and takeout all the=20
> #if directives.
>=20
> -----Original Message-----
> From: nmo...@li...
> [mailto:nmo...@li...] On=20
> Behalf Of aci...@ac...
> Sent: Thursday, November 08, 2007 2:39 PM
> To: NMock2 Development Discussion
> Subject: [NMock2-Dev] NMock Cleanup
>=20
> I've been thinking about what we need to do to make NMock2=20
> really look alive again, and while the new RC that should be=20
> coming soon will be a big boost we need to cleanup=20
> SourceForge and the website so that we aren't showing=20
> outdated information.
>=20
> Proposals:
>=20
> Close all bugs/Support requests that are not related to NMock2.
> Import the current nmock2 directory from CVS into Subversion=20
> to get away from NMock 1.0 legacy code.
> Update the SourceForge developer list to reflect current=20
> developers Decide who should have commit access to the code.
>=20
> There are more ideas floating around in my head and when I=20
> can articulate them I'll send them on. Discussion on these=20
> ideas is welcome and encouraged.
>=20
> -Richard Holden
>=20
>=20
> --------------------------------------------------------------
> ----------
> -
> 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=20
> a browser.
> Download your FREE copy of Splunk now >>=20
> http://get.splunk.com/ _______________________________________________
> NMock-two-dev mailing list
> NMo...@li...
> https://lists.sourceforge.net/lists/listinfo/nmock-two-dev
>=20
> --------------------------------------------------------------
> -----------
> 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=20
> a browser.
> Download your FREE copy of Splunk now >>=20
> http://get.splunk.com/ _______________________________________________
> NMock-two-dev mailing list
> NMo...@li...
> https://lists.sourceforge.net/lists/listinfo/nmock-two-dev
>=20



------------------------------------------------------------------------
-
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