|
From: Steve F. <st...@m3...> - 2007-11-08 21:32:42
|
Can I also suggest you take a look at jMock2? The new syntax allows refactoring, a la Rhino, but is better IMHO. S On 8 Nov 2007, at 20:39, aci...@ac... wrote: > 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 > Steve Freeman Winner of the Agile Alliance Gordon Pask award 2006 http://www.m3p.co.uk M3P Limited. Registered office. 2 Church Street, Burnham, Bucks, SL1 7HZ. Company registered in England & Wales. Number 03689627 |