|
From: Steve M. <Ste...@ty...> - 2007-10-12 14:55:24
|
Sorry, I accidentally deleted the thread for this, so I don't have the original to respond to. =20 I am not having issues with the current hosting, so I don't see any reason to change the version control at this time just for the sake of change. I've already got CVS and SVN loaded for other purposes and I imagine that a lot of other developers already do as well. That being said, I do think that dealing with SVN is easier than CVS for me personally. I haven't dealt with Codeplex directly yet, so I can't comment on that. =20 As for the .NET 3.5 stuff, I've mentioned similar desires a few months ago, although I've not had the time to flesh them out. I also didn't find out about the () =3D> style of lambas until recently. We should definitely begin pursuing this in a 3.5 branch. =20 What I am more concerned about right now is the following: 1. We need to clean up the bug database, if we don't decide to move the project, and determine which bugs are actually NMock2 and need to be fixed and close out the rest. From this perspective, a distinct break from the old NMock stuff by rehosting might be beneficial, but certainly not needed. 2. We need to designate someone to act as the official builder and produce a new build one all the bugs we want fixed are fixed. 3. We need to update the website information to reflect the new syntax of the event model. =20 Following that, we need to produce a roadmap to the next version, the open areas of discussion that I've seen are 1. .NET 3.5 support with new syntax 2. Replacing the TransparentProxy with Castle.Dynamic proxy or some other full featured proxy. =20 =20 |