From: larry.jones@sdrc.com (Larry Jones)
To: ttm@online.no
Cc: info-cvs@gnu.org
Date: Fri, 1 Jun 2001 14:31:21 -0400 (EDT)
Subject: Re: CVS and assesment
Message-Id: <200106011831.OAA01311@thor.sdrc.com>
X-Mailer: ELM [version 2.4 PL25]

Thomas Tuft Muller writes:
> 
> I imagine a scenario where each
> programmer is forced to check in once a week (preferrably with a specific
> tag indicating that the files are possibly untested/uncompilable). Proper
> scripts could analyze the code regarding inter alia number of
> lines/words/bytes, commenting, commenting rules, coding-rules, class
> cohesion, method-length, class-length, parameter names, variable names,
> etc,
> etc. In addition the scripts should also take into account the state of
> the
> archive last time the scripts were run, and analyze/provide statistics
> about
> the change.
> 
> Combined with a weekly/monthly submitted timeplan from the programmers,
> this
> could be a valuable tool for managers to see the overall as well as
> individual progress/quality.
> 
> Does such analying scripts exist for the CVS archive format?

I sincerely hope not.

-Larry Jones

Hmph. -- Calvin

_______________________________________________
Info-cvs mailing list
Info-cvs@gnu.org
http://mail.gnu.org/mailman/listinfo/info-cvs