On Sun, May 20, 2012 at 4:16 PM, Ted Byers <r.ted.by...@gmail.com> wrote:
> I have read arguments that recommend
> against this, claiming it can slow down commits, but then I am more
> concerned about code quality, and always having a codebase, which to me
> includes all tests, that compiles and runs properly than I am in the
> convenience of any programmers working on the project.
I suspect that everyone involved would be happier if you implement
that in a continuous integration tool like jenkins that will still
check everything (and can do a lot more) but does not interfere with
commits. And use branches/tags to identify the production quality
versions so your programmers can get some work done.
--
Les Mikesell
lesmikes...@gmail.com
