Nice to hear from you. Hope your project is going well.
Looks like there's been quite a few questions, more than I can keep up
with! I'll try to answer your questions, but understand I'm a bit
swamped because I've got four assignments due Friday. Ah, the life of
> how does incremental stats collection work for, say, number of commits
> I would have assumed that collecting this data incrementally would mean
> that values grow or stay the same.
That's exactly how it works. If the graph is marked as 'incremental',
then for each new datapoint, we report the sum of all the datapoints
gathered so far.
Take a look at one of the CVS Operations graph, for example:
> where would be the least painful way to
> insert a clause "if the case of new metric, process db table in the
> follwoing way..."
You're asking how to change the way that metrics are processed after
they have been added to the database? That's actually quite easy --
not painful at all! :)
Let's say you wrote a class for processing metrics called
'PerDeveloperScatterPlot', following the same convention as the other
classes in the Report package such as PerDeveloperTimeSeries.
If you want to display any metric using your new class, simply specify
as such in your sample_config.txt. Instead of specifying simply
'CodeSize-PerDeveloper', specify 'CodeSize-PerDeveloperScatterPlot'.
Then, instead of displaying the number of classes as a per developer
pie graph, you'll display it as a scatter plot!
Hope that helps!