statcvs-users — StatCVS Users Mailing List

Re: [Statcvs-users] Release early and often?

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

Hi Jukka,

Thanks for the thoughtful response! Responses/questions inline.

Am 24.03.2005 um 21:40 schrieb Jukka Uusisalo:
[...]
> How about process as follows:
>
> 1. Decide what new features are in next release
>
> 2. Provide nightly-build. Nightly-build is released from cvs head 
> branch if there are any changes in cvs, code gets compiled and passes 
> unit tests.
>
> 3. When all features in next release are implemented, provide 
> release-candidate. This point there should be branch in cvs for 
> release-
> candidate bugfixes. Propably you will need couple of 
> release-candidates.
>
> 4. When you think release-candidate is stable enough, just release 
> official release or maybe uses take a vote, but propably everybody 
> will use some release candidate as production at this point.

I think I'd rather skip #1. StatCVS contributions (including my own) 
come from people scratching an itch, and it's kind of hard to plan 
that. So I'd rather just wait until there's enough new stuff.

Having a release candidate branch seems like a good idea. This means 
work on new stuff can continue while the candidate matures.

Any guesses how long we might have to stay in RC mode before the 
candidate is well-tested enough?

Also, is it worth the trouble for such a small project? I don't want to 
spend much time managing the process.


> Nighly-builds requires automated build system and good enough unit test
> cases. Do you have checked coverage of unit tests?

I like the idea of nightly builds. Get the new stuff out as fast as 
possible.

Our test coverage is not too good, especially in the HTML output code. 
But I wouldn't worry about that too much, the most important parts are 
well-tested. I believe that nightly builds would drive test quality 
because we would actually rely on the tests.

Any recommendations for a test coverage tool? (I guess the answer will 
have something to do with Maven :-)

How could we implement nightly builds with SourceForge? Just run Ant or 
Maven with a cronjob and dump the dist file on the SourceForge project 
web server? Anyone has experience with that?

Questions, questions, questions ...


> - Jukka -

Richard

Re: [Statcvs-users] Release early and often?

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

Hi Martin,

Am 23.03.2005 um 23:42 schrieb Martin d'Anjou:

[...]
> In other words, a good the test suite speeds up stable releases. If you
> don't have a good test suite, then you have to rely on users' 
> generosity.

That's a good point. With a good test suite, the code likely has less 
bugs and no regressions. This means you can release with greater 
confidence.

I wouldn't go as far as saying that you safely can do a stable release 
if all tests pass. A green bar is no guarantee that your software is 
bug-free and fulfills user's requirements.

The stuff that you can't catch with a test suite (e.g. problems with 
certain system configurations) is unlikely to be found without a bit of 
circulation. I guess that's the rationale for doing beta builds or 
release candidates.

Richard

Re: [Statcvs-users] Release early and often?

[Jukka U. <juk...@dn...>]

Richard Cyganiak kirjoitti:
> 
> What do you think? How should an open source release process for a 
> project like StatCVS work? Both developer's and user's point of views 
> are welcome.
> 

Hi,

This is pretty intresting question. I think it is good idea to make time 
between releases so short as possible, but not shorter than possible. I
mean if you have certain process, it will take certain time and if you 
try to make it faster, you don't follow your process. Only way is 
improve your process. And now we discussing how to improve statcvs 
release process.

How about process as follows:

1. Decide what new features are in next release

2. Provide nightly-build. Nightly-build is released from cvs head branch 
if there are any changes in cvs, code gets compiled and passes unit tests.

3. When all features in next release are implemented, provide 
release-candidate. This point there should be branch in cvs for release-
candidate bugfixes. Propably you will need couple of release-candidates.

4. When you think release-candidate is stable enough, just release 
official release or maybe uses take a vote, but propably everybody will 
use some release candidate as production at this point.

Nighly-builds requires automated build system and good enough unit test
cases. Do you have checked coverage of unit tests?

Like Martin says good test suite is important thing, but i assume that
application like statcvs, good unit test suite has most effort for 
testing. There are no user interactions etc, which are hard to test with
junit.

In open source projects, tight schedules aren't critical issue. People 
are voluntarily working and everybody has possibility to contribute to 
get releases ready earlier.

- Jukka -

Re: [Statcvs-users] New parameter '-tags'

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

On Wednesday 23 March 2005 03:35 pm, Richard Cyganiak wrote:
> By the way, I have a dumb question: How do I apply such a diff output
> automatically to a file? Something with the patch command I believe,
> but I couldn't get it to work.

if your diff file is named 'tagspatch.diff'

you would do:

patch < tagspatch.diff

to apply the patch.

Generally, this works best when the diff is against only a small number of 
files, and if the diff is a 'unitified' diff.

diff -u3 origfile changedfile >> filename.patch

The -u3 parameter to diff is very important, because it creates a 'unified'
diff with several lines of context.  This allows the patch program to find
where to insert the changed lines, even if the file has changed slightly
since the patch was generated.

Regards,

   - Brian

Re: [Statcvs-users] New parameter '-tags'

[Jukka U. <juk...@dn...>]

Richard Cyganiak wrote:
> Hi Jukka,
> 
> Am 21.03.2005 um 21:34 schrieb Jukka Uusisalo:
> 
>> Here is also attached diff for support
>> tags attribute in statcvs ant task too.
> 
> 
> Thanks! Committed to CVS.
> 
>> But how about show tags also file count graph and loc by module graphs?
> 
> 
> I await your patch ;-)
> 

Let's see, what can i do. :)


> By the way, I have a dumb question: How do I apply such a diff output 
> automatically to a file? Something with the patch command I believe, but 
> I couldn't get it to work.
>

I have also a dumb answer :) I just use eclipse and apply patch 
functionality but i am sure there is better way to do that.

Maybe you can add guide how-to-contribute-statcvs to statcvs web site,
so we can contribute way what is the most easiest for you.

- Jukka -


> Richard
> 
> 
> 
>> Index: StatCvsTask.java
>> ===================================================================
>> RCS file: 
>> /cvsroot/statcvs/statcvs/src/net/sf/statcvs/ant/StatCvsTask.java,v
>> retrieving revision 1.11
>> diff -r1.11 StatCvsTask.java
>> 52a53
>>
>>>     private String tags;
>>
>> 117a119,121
>>
>>>         if (tags != null) {
>>>             ConfigurationOptions.setSymbolicNamesPattern(this.tags);
>>>         }
>>
>> 200a205,212
>>
>>>     /**
>>>      * Specifies regular expression to include tag to lines
>>>      * of code graph.
>>>      * @param tags regular expression to included tags names.
>>>      */
>>>     public void setTags(String tags) {
>>>         this.tags = tags;
>>>     }
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
> Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
> Embedded(r) & Windows Mobile(tm) platforms, applications & content.  
> Register
> by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click
> _______________________________________________
> Statcvs-users mailing list
> Sta...@li...
> https://lists.sourceforge.net/lists/listinfo/statcvs-users
> 
> 

Re: [Statcvs-users] Release early and often?

[Martin d'A. <md...@ne...>]

> What do you think? How should an open source release process for a 
> project like StatCVS work? Both developer's and user's point of views 
> are welcome.

I am really interested in people's opinions as well. Note that I have not
used StatCVS in years. So forgive me for stating the obvious here.

Software evolves by making bug fixes or adding features (by adding 
features I mean the general sense including code rewrites that does not 
necessarily add a feature visible to the user - like restructuring code
for future developments). So I am going to consider two cases: bug and 
features in the release process. Then there are the tests for the bug or 
the specific feature and the existing test suite, and then whether a 
stable release should be made or not depending on the result of the test

Case   Test for bug/feature Existing test  Stable release?
       has passed           suite passed
bug    yes                  yes            yes
bug    yes                  no             no
bug    no                   yes            only if there are new features
                                           in the release and the tests 
                                           for those have passed
feat.  yes                  yes            yes
feat.  yes                  no             no
feat.  no                   yes            only if there are bug fixes
                                           in the release and the tests
                                           have passed

In other words, a good the test suite speeds up stable releases. If you 
don't have a good test suite, then you have to rely on users' generosity.

Martin

PS: Here is another view of the same table for those with whitespace 
impaired email clients:

<table>
<th>
<td>Case</td>
<td>Test for bug/feature has passed</td>
<td>Existing test suite has passed</td>
<td>Do a stable release?</td>
</th>
<tr>
<td>bug</td>
<td>yes</td>
<td>yes</td>
<td>yes</td>
</tr>
<tr>
<td>bug</td>
<td>yes</td>
<td>no</td>
<td>no</td>
</tr>
<tr>
<td>bug</td>
<td>no</td>
<td>yes</td>
<td>only if there are new features in the release and the tests for those have passed</td>
</tr>

<tr>
<td>feature</td>
<td>yes</td>
<td>yes</td>
<td>yes</td>
</tr>
<tr>
<td>feature</td>
<td>yes</td>
<td>no</td>
<td>no</td>
</tr>
<tr>
<td>feature</td>
<td>no</td>
<td>yes</td>
<td>only if there are bug fixes in the release and the tests for those have passed</td>
</tr>

</table>

[Statcvs-users] Release early and often?

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

Hi all,

Brian's request for a dev snapshot made me think about the StatCVS 
release process.

I tend to release late. New features and bugfixes can sit in the CVS 
for many month before I put together a new release. That's because I 
often feel that the new features need more testing and are not yet 
stable enough. I don't want to release a new version with significant 
new bugs.

But recently I think that this is the wrong strategy. Common wisdom in 
the open source community is to "release early, release often". And 
when people rely on inofficial dev builds because important new 
features and bugfixes are not available in the official release, then 
the process is obviously broken.

So what can I do to improve the release process?

Publish release candidates?

Offer a stable and a beta download?

Just stop worrying about bugs and release without much testing?

Other ideas?

What do you think? How should an open source release process for a 
project like StatCVS work? Both developer's and user's point of views 
are welcome.

Thanks,
Richard

Re: [Statcvs-users] New parameter '-tags'

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

Hi Jukka,

Am 21.03.2005 um 21:34 schrieb Jukka Uusisalo:
> Here is also attached diff for support
> tags attribute in statcvs ant task too.

Thanks! Committed to CVS.

> But how about show tags also file count graph and loc by module graphs?

I await your patch ;-)

By the way, I have a dumb question: How do I apply such a diff output 
automatically to a file? Something with the patch command I believe, 
but I couldn't get it to work.

Richard



> Index: StatCvsTask.java
> ===================================================================
> RCS file: 
> /cvsroot/statcvs/statcvs/src/net/sf/statcvs/ant/StatCvsTask.java,v
> retrieving revision 1.11
> diff -r1.11 StatCvsTask.java
> 52a53
>> 	private String tags;
> 117a119,121
>> 		if (tags != null) {
>> 			ConfigurationOptions.setSymbolicNamesPattern(this.tags);
>> 		}
> 200a205,212
>> 	/**
>> 	 * Specifies regular expression to include tag to lines
>> 	 * of code graph.
>> 	 * @param tags regular expression to included tags names.
>> 	 */
>> 	public void setTags(String tags) {
>> 		this.tags = tags;
>> 	}

Re: [Statcvs-users] Development Build with -tags

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

Hi Brian,

Am 23.03.2005 um 14:53 schrieb Brian G. Peterson:

> Could one of the StatCVS developers (Richard?) perhaps post a 
> development
> build .jar file with the new -tags option in it?
>
> I don't have a working ant development environment right now, as I'm 
> not doing
> Java development at my current employer, so if I can avoid creating 
> one for
> the moment, it would make my life a little easier.

C'mon, what a lame excuse ;-)

Here you go: http://page.mi.fu-berlin.de/~cyganiak/temp/statcvs.jar

Richard

[Statcvs-users] Development Build with -tags

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

Could one of the StatCVS developers (Richard?) perhaps post a development 
build .jar file with the new -tags option in it?

I don't have a working ant development environment right now, as I'm not doing 
Java development at my current employer, so if I can avoid creating one for 
the moment, it would make my life a little easier.

Thanks in advance for the assistance.

Regards,

   - Brian

Re: [Statcvs-users] StatCVS - repository access

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

Hi Lavinia,

Am 23.03.2005 um 06:04 schrieb lavinia:

> Dear All,
> =A0
> We have analysed the reports generated by StatCVS and they seem to be=20=

> quite good. Information provided by StatCVS is self explanatory and=20
> lucid.

Thanks!

> We now require one information from you. We would like to know which=20=

> is the class file that accesses the CVS repository to derive all the=20=

> required information needed as per the necessity. This is=A0our=20
> current=A0necessity.=A0Based on that we could retrieve only required=20=

> information and not all possible information that CVS Stat does.

Depends on what kind of filtering you want to do. Filtering by=20
directory or file name is already supported through the -include und=20
-exclude options. Some filtering is done best at the input/parsing=20
stage. Or when the actual report is generated (e.g. when you want to=20
filter only for some kinds of reports).

Can you give us more information? What kind of information do you want=20=

to keep out of the report?

Thanks,
Richard



> =A0
> Could you please help us out in this issue. Thanking you in adv.
> =A0
> Expecting your kind co-operation in this regard.
> =A0
> Kind Regards,
> Lavinia.
> =A0
> =A0

[Statcvs-users] StatCVS - repository access

[lavinia <la...@gf...>]

Dear All,

We have analysed the reports generated by StatCVS and they seem to be =
quite good. Information provided by StatCVS is self explanatory and =
lucid.=20

We now require one information from you. We would like to know which is =
the class file that accesses the CVS repository to derive all the =
required information needed as per the necessity. This is our current =
necessity. Based on that we could retrieve only required information and =
not all possible information that CVS Stat does.

Could you please help us out in this issue. Thanking you in adv.

Expecting your kind co-operation in this regard.

Kind Regards,
Lavinia.

Re: [Statcvs-users] New parameter '-tags'

[Jukka U. <juk...@dn...>]

Richard Cyganiak wrote:
> Hi Steffen,
> 
> Am 20.03.2005 um 20:21 schrieb Steffen Pingel:
> 
>> I have added a new comman line parameter named -tags. It takes a regular
>> expression as its argument that specifies the tags to include in the loc
>> charts. Here a two examples:
> 
> 
> Great! I just tried it and it works like a charm.
> 

Hi,

I also tried that in my build server and windows box
and it works fine. Here is also attached diff for support
tags attribute in statcvs ant task too.


>>  -tags '.*'  matches all tags
> 
> 
> Maybe there should be an easier way to use this?
> 
>    -tags all
> 
> or just
> 
>    -tags
> 
> without a regex?
>

These are good ways both but i can live with '.*'. But how about show 
tags also file count graph and loc by module graphs?


- Jukka -


>> If the -tags parameter is omitted no tags will be displayed.
> 
> 
> Yeah, this is a good default.
> 
> Cheers,
> Richard
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Statcvs-users mailing list
> Sta...@li...
> https://lists.sourceforge.net/lists/listinfo/statcvs-users
> 
> 

Re: [Statcvs-users] New parameter '-tags'

[Steffen P. <ste...@gm...>]

Hi,

> Maybe there should be an easier way to use this?
[...]
>     -tags
>
> without a regex?

Yes, I agree, that would be the best way to go. Unfortunatelly the command 
line parser does not yet support optional arguments. 

Steffen

-- 
Steffen Pingel - ste...@gm... - http://steffenpingel.de

Re: [Statcvs-users] New parameter '-tags'

[Steffen P. <ste...@gm...>]

Hi,

> Cool, but where is the code? I just browsed sourcefor statcvs cvs-
> repository, but i didn't see anything new?

I guess it will take a few hours until the changes become visible in viewcvs 
and the anonymous cvs. The last time I checked, SourceForge ran the 
synchronization every five hours.

I have attached a patch that contains the changes.

Steffen

-- 
Steffen Pingel - ste...@gm... - http://steffenpingel.de

Re: [Statcvs-users] New parameter '-tags'

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

Am 20.03.2005 um 23:51 schrieb Jukka Uusisalo:

> Steffen Pingel kirjoitti:
>> Hi,
>> I have added a new comman line parameter named -tags. It takes a 
>> regular expression as its argument that specifies the tags to include 
>> in the loc charts. Here a two examples:
>>  -tags '.*'  matches all tags
>>  -tags '^v\d_.*' matches all tags that start with a 'v' followed    
>> by a number and an underscore
>>   This page has a complete description of Sun's regexp syntax: 
>> http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html 
>> .
>> If the -tags parameter is omitted no tags will be displayed.
>> Steffen
>
> Hi,
>
> Cool, but where is the code? I just browsed sourcefor statcvs cvs- 
> repository, but i didn't see anything new?

SourceForge's anonymous CVS often lags a few hours behind the actual 
repository. Quite annoying.

Richard


>
> - Jukka -
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real 
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Statcvs-users mailing list
> Sta...@li...
> https://lists.sourceforge.net/lists/listinfo/statcvs-users
>

Re: [Statcvs-users] New parameter '-tags'

[Jukka U. <juk...@dn...>]

Steffen Pingel kirjoitti:
> Hi,
> 
> I have added a new comman line parameter named -tags. It takes a regular 
> expression as its argument that specifies the tags to include in the loc 
> charts. Here a two examples:
> 
>  -tags '.*'  matches all tags
>  -tags '^v\d_.*' matches all tags that start with a 'v' followed 
>    by a number and an underscore
>   
> This page has a complete description of Sun's regexp syntax: 
> http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html .
> 
> If the -tags parameter is omitted no tags will be displayed.
> 
> Steffen
> 

Hi,

Cool, but where is the code? I just browsed sourcefor statcvs cvs- 
repository, but i didn't see anything new?

- Jukka -

Re: [Statcvs-users] New parameter '-tags'

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

Hi Steffen,

Am 20.03.2005 um 20:21 schrieb Steffen Pingel:
> I have added a new comman line parameter named -tags. It takes a 
> regular
> expression as its argument that specifies the tags to include in the 
> loc
> charts. Here a two examples:

Great! I just tried it and it works like a charm.

>  -tags '.*'  matches all tags

Maybe there should be an easier way to use this?

    -tags all

or just

    -tags

without a regex?

> If the -tags parameter is omitted no tags will be displayed.

Yeah, this is a good default.

Cheers,
Richard

[Statcvs-users] New parameter '-tags'

[Steffen P. <ste...@gm...>]

Hi,

I have added a new comman line parameter named -tags. It takes a regular 
expression as its argument that specifies the tags to include in the loc 
charts. Here a two examples:

 -tags '.*'  matches all tags
 -tags '^v\d_.*' matches all tags that start with a 'v' followed 
   by a number and an underscore
  
This page has a complete description of Sun's regexp syntax: 
http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html .

If the -tags parameter is omitted no tags will be displayed.

Steffen

-- 
Steffen Pingel - ste...@gm... - http://steffenpingel.de

[Statcvs-users] Re: StatCVS

[Scott R. <sc...@in...>]

Richard,

Thanks for the prompt response.  If anyone would be interested in 
helping us to do the integration into the oda, that would be great too.

Scott

pe...@bl... wrote:

>Scott,
>
>its an honor that other people show interest in statcvs. From my personal
>point of view you can use our source for integration into BIRT without
>restriction - well a reference that statcvs code has been used and what
>for would be nice. But I have to ask the other members of the statcvs team
>for their approval.
>I sent this email CC to the statcvs mailing list. As soon as I have the
>feedback from the team, I will contact you.
>Keep going,
>Lukasz
>
>  
>
>>Lukasz,
>>
>>I recently stumbled across the StatCVS project while browsing the IBM
>>developer works RSS feeds.  It looks like you have a really
>>initeresting  project.  I am currently on the Eclipse Business
>>Intelligence and  Reporting Tools (BIRT) project management committee.
>>BIRT can be found  at (http://eclipse.org/birt).  Our goal is to create
>>a common reporting  frame work that is accessible to any one in the
>>Java community.  One of  the things that we have discussed is the
>>ability to report against data  in CVS databases.
>>Lo and behold, someone has beat us to the punch.
>>
>>I wonder if there is a way that statCVS and BIRT could work together.
>>The BIRT project contains the concept of an Open Data Adapter (ODA).
>>It  seems like it should be relatively easy to use some of the StatCVS
>>code  to create a BIRT data adapter.  Once the data is brought into
>>BIRT, we  can use the standard BIRT tools to format and render the
>>information.   BIRT will have full formatting and graphics options
>>available.
>>
>>I don't want to steal something away that you have been clearly working
>> on for a long time.  I am more interested in seeing how good BIRT is
>>at  this type of application.  We have had a great deal of interest
>>from  within the Eclipse community in regards to reporting on their
>>projects.
>>
>>If you are interested / intrigued at all, please let me know and we can
>> talk about next steps.
>>
>>Scott Rosenbaum
>>BIRT PMC
>>    
>>
>
>
>
>
>  
>

[Statcvs-users] Re: StatCVS

[<pe...@bl...>]

Scott,

its an honor that other people show interest in statcvs. From my personal
point of view you can use our source for integration into BIRT without
restriction - well a reference that statcvs code has been used and what
for would be nice. But I have to ask the other members of the statcvs team
for their approval.
I sent this email CC to the statcvs mailing list. As soon as I have the
feedback from the team, I will contact you.
Keep going,
Lukasz

> Lukasz,
>
> I recently stumbled across the StatCVS project while browsing the IBM
> developer works RSS feeds.  It looks like you have a really
> initeresting  project.  I am currently on the Eclipse Business
> Intelligence and  Reporting Tools (BIRT) project management committee.
> BIRT can be found  at (http://eclipse.org/birt).  Our goal is to create
> a common reporting  frame work that is accessible to any one in the
> Java community.  One of  the things that we have discussed is the
> ability to report against data  in CVS databases.
> Lo and behold, someone has beat us to the punch.
>
> I wonder if there is a way that statCVS and BIRT could work together.
> The BIRT project contains the concept of an Open Data Adapter (ODA).
> It  seems like it should be relatively easy to use some of the StatCVS
> code  to create a BIRT data adapter.  Once the data is brought into
> BIRT, we  can use the standard BIRT tools to format and render the
> information.   BIRT will have full formatting and graphics options
> available.
>
> I don't want to steal something away that you have been clearly working
>  on for a long time.  I am more interested in seeing how good BIRT is
> at  this type of application.  We have had a great deal of interest
> from  within the Eclipse community in regards to reporting on their
> projects.
>
> If you are interested / intrigued at all, please let me know and we can
>  talk about next steps.
>
> Scott Rosenbaum
> BIRT PMC

Re: [Statcvs-users] Merged Branch Patch from Atlassian

[Steffen P. <ste...@gm...>]

Hi,

> BTW, sometime ago there was discussion about filtering tags, (symblic
> names patch). Do you have worked about that?

Sorry, totally forgot about that. Should be a trivial patch (as the code 
already exists in StatCvs-XML). I'll have a look at it tomorrow.

Steffen

-- 
Steffen Pingel - ste...@gm... - http://steffenpingel.de

Re: [Statcvs-users] Merged Branch Patch from Atlassian

[Jukka U. <juk...@dn...>]

Steffen Pingel wrote:
> 
> I am not quite sure what everybody expects from branch support (just analyse a 
> single branch? or mutliple branches? or include the head branch up to the 
> point where the branch was forked?). 
> 

My vote is something like last option. With branches i like to see point 
where the brach has forked, how much they differs comparing to the head, 
  lines of code graph and maybe number of commits graph and finally 
point when they are merged back.

BTW, sometime ago there was discussion about filtering tags, (symblic 
names patch). Do you have worked about that?

- Jukka -

[Statcvs-users] Merged Branch Patch from Atlassian

[Steffen P. <ste...@gm...>]

Hi,

a few weeks ago I received the patch that adds branch support from Scott from 
Atlassian (thanks btw!). Unfortunately the merge did not work out too well, 
since the patch had been diffed against the repository quite a while ago. 
Part of the model classes had changed and the patch conflicted with the 
symbolic names support as it naturally touched the same parts of the code.

Anyways, I just finished a first working branch support implementation based 
on the patch. I decided to take a take a slightly different approach than the 
original patch though. If understood the code correctly, the original patch 
limits the analysis to a single branch, whereas in my implementation  all 
branches that are contained in the log file are added to the model and can 
therefore be analysed. 

Here is an example of the generated output of an analysis of a single branch : 
http://statcvs-xml.berlios.de/branches/branch_branch-support-1-branch.html. 
The commit log on the bottom shows that the revisions are indeed on a branch.

And here is an example comparing three branches: 
http://statcvs-xml.berlios.de/branches/branch_stats.html

The log file was generated by running 'cvs log 
-rbranch-support-1-branch,:HEAD,statcvs' on the statcvs-xml cvs.

I still need to figure out how to calculate the loc correctly but at least the 
parser seems to work. If anybody want to look at the code, it is located in 
the statcvs-xml cvs (http://statcvs-xml.berlios.de/cvs-usage.html) in the 
'branch-support-1-branch' branch.

I am not quite sure what everybody expects from branch support (just analyse a 
single branch? or mutliple branches? or include the head branch up to the 
point where the branch was forked?). 

If anyone want to discuss this or tweak the code, please get in touch with me. 
Either by means of this list or private email.

Steffen

-- 
Steffen Pingel - ste...@gm... - http://steffenpingel.de

Re: [Statcvs-users] statcvs: exclution

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

Hi Mike,

you can do that like this:

    java -jar statcvs.jar -exclude somedir/**:**/*.xyz ...(other =
options)

This excludes everything in the "somedir" directory and all files=20
ending in .xyz.

More info:

    http://statcvs.sourceforge.net/manual/#section_command-line-options

Hope that helps,
Richard


Am 07.03.2005 um 19:08 schrieb Nereson Michael R SrA 805 CSPTS/SCE:

> Is there a way to exclude directories or files that statcvs reports =
on?
>
> For example, under my project root, I have my prototype files and my=20=

> source files. I don=92t want any of the prototype files to be =
considered=20
> in the statcvs reports.
>
> Thanks for any help that can be provided.
>
> ~ Mike