One reason I haven't contributed much in terms of code for quite some time is the ever changing technology stack Tapestry is built with. We have an increasingly complex stack of bleeding-edge tools and technologies that I simply lack the time of keeping up with.
I have the feeling that this might be a turn-down for other potential contributors as well. I won't be against it but don't be surprised about continously declining contributor activity. Uli On 30.07.2013 23:50, Howard Lewis Ship wrote: > One thing I've been saying in some of the bugs I've been closing is my > desire to get out of the testing side of things. I have no desire to > maintain the existing TestNG, EasyMock, and Selenium support code ... you > may have noticed that I'm a fan of Spock for unit and mock testing, and Geb > for end-to-end integration testing. > > I'd love to scrap the existing tapestry-core tests and rewrite for Spock > and Geb, but (alas), that is a huge effort. But I would like to start > documenting in release notes and elsewhere that the path forward is to > invest in Spock and Geb. > > Ok ... as usual, since I've been thinking about this in the background for > too long, my invitation to discuss sounds like a mandate ... but, > seriously, thoughts on this subject? > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
