Re: Projects?

Files wrote:

>
> /me votes +1 for mimicking log-cmd.c and reporting a count instead.
>
> The point is not the revisions total. The point is to be able to determine
> frequency/stability.
>

I don't think that frequency of changes in a file has any guarantee of implying
stability. I can definitely imagine a large .c file which contains subtle bugs,
but is so monolithic that no one has been able to track them down, hence the
other source code files contain workarounds for the bad code. The only thing
that a small change count guarantees is that no one has made many changes.

For example, 10 changes in the course of the last year is a very different
statement from 10 changes in the last day (or week or month). If, for example,
you wanted to produce a velocity (changes/time period), it would denote
something more useful, but it would still be a very imprecise measure.

My 2 cents

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org