statcvs-users

[Statcvs-users] CVS

[Nitin W. <np...@oa...>]

Hi,

I just wanted to know what kind of data is available from CVS.
Like breakdown of bugs fixed per developer, reports, version release =
etc...

Please let me know what else is available from CVS and then we can see =
whether we can compensate you for your efforts.

Thanks

Nitin Walia
Oakland University

[Statcvs-users] CVS

[llchen <ll...@me...>]

aGkgLA0KDQp3aHkgbXkgc3RhdGN2cyBjYW4gbm90IHN0c3Rpc3RpYyBjYWNjdXJhdGVseQ0K

Re: [Statcvs-users] CVS

[Richard C. <ri...@cy...>]

Hi,

> why my statcvs can not ststistic caccurately

could you please be more specific?

Re: [Statcvs-users] CVS

[Brian G. P. <br...@br...>]

On Thursday 14 October 2004 11:04 am, Nitin Walia wrote:
> I just wanted to know what kind of data is available from CVS.
> Like breakdown of bugs fixed per developer, reports, version release etc...

CVS is the version control system that stores code changes.  All revision 
information on the project is stored in CVS.

StatCVS is the best tool I'm aware of for analyzing and presenting that 
information.  I've used StatCVS for several years on both open source and 
closed source projects, and find it invaluable in assiting me in managing 
project resources.  StatCVS will provide ststistics like lines per change, 
changes per developer, histograms of when changes are being made, and many 
more.  

You can see a sample set of StatCVS reports on the StatCVS web site here:
http://statcvs.sourceforge.net/statcvs-stats/
another example, for the open source CRM project XRMS, is here:
http://www.explorerfunds.com/dev/xrmsstats/

Bug reporting and tracking is a tool for a different application, like 
Bugzilla or Mantis.  Both of the Bug tracking applications I've mentioned can 
be integrated with CVS (your version control system) so that there are 
linkages between the change made to fix the bug and the bug report.  

StatCVS will show you the commit comments on each change made to the code in 
an easy to navigate format, so you'll be able to see the bug numbers and 
comments that are linked to commit comments, if you've implemented 
integration as I described in the previous paragraph.  StatCVS doesn't 
replace a bug tracking system, but can supplement the reporting available and 
make the project manager's life easier.

I also tend to make extensive use on my projects of automated code 
documentation tools, like JavaDoc and PHPDoc (in Java and PHP), as these 
integrate well with CVS, StatCVS, Bugzilla, xUnit unit testing, and other 
development tools to provide complete development documentation.

> Please let me know what else is available from CVS and then we can see
> whether we can compensate you for your efforts.

I'm a satisfied StatCVS user for many years and across many projects, some of 
which ran to millions of lines of code, and can highly recommend it for your 
development projects.  My opinions are my own, and do not necessarily reflect 
the opinions of the StatCVS development team.

Regards,

   - Brian
 

Re: [Statcvs-users] CVS

[Richard C. <ri...@cy...>]

Nitin,

Am 14.10.2004 um 18:04 schrieb Nitin Walia:
> I just wanted to know what kind of=A0data is available from CVS.
> Like breakdown of bugs fixed per developer, reports, version release=20=

> etc...

from our previous communications I assume that you are interested in=20
data for statistical analysis across a large number of projects, for=20
research purposes?

You already know that CVS log data can be used to quantify individual=20
developer contribution over time and code area (insert disclaimer here=20=

about validity of Lines of Code as a productivity measure).

CVS Tags and CVS Branches can provide some insight into the versions=20
and releases of a software product. Time between releases, number and=20
patterns of commits between releases etc.

Brian has already pointed out that CVS comments are often used to refer=20=

to bug numbers from bug tracking software. These CVS comments might be=20=

used to analyse # of bugs fixed per developer, time of bugfixes and=20
similar things.

On a related note: You have already mined SourceForge.net for CVS data.=20=

SourceForge also provides bug trackers for projects, similar to those=20
mentioned by Brian. You might use screen scraping technology to extract=20=

data about bugs from these trackers (date opened, date closed,=20
developers involved). CVS comments might be used to cross-correlate=20
this data with data from the CVS.

The problem with all those data sources is that they are not used in=20
the same way across projects. Analysis would involve *much* more manual=20=

labour. That's why I'm not sure if that will be practical.

Best regards,
Richard=

Re: [Statcvs-users] CVS

[Scott F. <sc...@at...>]

On Fri, Oct 15, 2004 at 07:58:21PM +0200, Richard Cyganiak wrote:
> Brian has already pointed out that CVS comments are often used to refer 
> to bug numbers from bug tracking software. These CVS comments might be 
> used to analyse # of bugs fixed per developer, time of bugfixes and 
> similar things.
> 
> On a related note: You have already mined SourceForge.net for CVS data. 
> SourceForge also provides bug trackers for projects, similar to those 
> mentioned by Brian. You might use screen scraping technology to extract 
> data about bugs from these trackers (date opened, date closed, 
> developers involved). CVS comments might be used to cross-correlate 
> this data with data from the CVS.

Indeed, we use our own version of StatCVS to parse log files, and we use
that integration to integrate CVS with JIRA:

  http://www.atlassian.com/software/jira/docs/latest/cvs_integration.html

It even handles branches :)

Cheers,
Scott

Re: [Statcvs-users] CVS

[Richard C. <ri...@cy...>]

Scott,

Am 25.10.2004 um 15:09 schrieb Scott Farquhar:
> Indeed, we use our own version of StatCVS to parse log files, and we  
> use
> that integration to integrate CVS with JIRA:
>
>    
> http://www.atlassian.com/software/jira/docs/latest/ 
> cvs_integration.html

Looks very nice. Having issue tracking, CVS logs and ViewCVS tightly  
integrated seems like a good and useful thing to me.

> It even handles branches :)

What can it do? Just filter for a single branch, or more?

What do I have to do to get the source?

Best,
Richard

Re: [Statcvs-users] CVS

[Scott F. <sc...@at...>]

I can email it to you, or put it up on an FTP site if you want.

Also includes the ability to ignore number of calculated lines, and
therefore not require a local repository.

Basically we use it for more than just lines of code - we use the object
model in memory.

So we don't calculate lines of code for branches, we just navigate the
object model.

I'm not sure how generally useful it is, and we haven't had a chance to
merge it back in to the main trunk, but if someone is interested (or
interested in putting it back in to the main trunk), then let me know.

Cheers,
Scott

On Mon, Oct 25, 2004 at 03:59:01PM +0200, Richard Cyganiak wrote:
> Scott,
> 
> Am 25.10.2004 um 15:09 schrieb Scott Farquhar:
> >Indeed, we use our own version of StatCVS to parse log files, and we  
> >use
> >that integration to integrate CVS with JIRA:
> >
> >   
> >http://www.atlassian.com/software/jira/docs/latest/ 
> >cvs_integration.html
> 
> Looks very nice. Having issue tracking, CVS logs and ViewCVS tightly  
> integrated seems like a good and useful thing to me.
> 
> >It even handles branches :)
> 
> What can it do? Just filter for a single branch, or more?
> 
> What do I have to do to get the source?
> 
> Best,
> Richard
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Statcvs-users mailing list
> Sta...@li...
> https://lists.sourceforge.net/lists/listinfo/statcvs-users