[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: cvs and gnats link?

From: Schwenk, Jeanie
Subject: RE: cvs and gnats link?
Date: Tue, 18 Sep 2001 14:21:21 -0700

On the down side, it's a beta and it says it connects with cvsweb, any idea
how that differs from connecting with CVS?  Just because it says it works
with CVSweb does not imply it will work with CVS.  CVS works here just find
but I was never able to get cvsweb to work here.  I went over to viewcvs
which works fine as long as you don't want to diff in the browser, but I

I look forward to hearing the results of your testing.


-----Original Message-----
From: John Minnihan [mailto:address@hidden
Sent: Tuesday, September 18, 2001 2:10 PM
To: Schwenk, Jeanie
Cc: address@hidden; address@hidden; address@hidden
Subject: Re: cvs and gnats link?

Another reader pointed to something called 'cvszilla'.  If this works as 
indicated, it will glue Bugzilla and CVS together " the hip".

I intend to test this app & will be delighted if it functions as noted. 
  I was about to go down that path myself (writing such a tool).

address@hidden wrote:

> If we keep the cvs and bug tracking seperate, my life and the lives of the
> engineers will be more complicated when what we want in convenience.  
> .  We will have to place comments in cvs and in the bug tracking system
> independently.  
> .  When management wants a report, they want a 1:1 correspondence between
> what code was touched, the comments and a list of everyone who touched the
> file(s) in question.  It'll end up on my desk and I don't want to do it by
> hand.
> .  When a bug crops up, and they will, the management wants to "see" how
> are handling the issue ... they want to see these two items joined at the
> hip.  
> I'm not saying that these two items can't be kept separate but selling the
> idea that it's a much safer method of development would be much more
> difficult.  They want to see everything connected.  After the last snafu,
> their feeling "secure" is worth the time and effort to get CVS and a bug
> tracking system to work together.   
> Jeanie
>>What would you ever enter twice? Bug reports go into GNATS, code goes
>>into CVS.
>>In your bug tracking system, you can make certain references to versions.
>>For example, a bug can be marked as having been discovered in 
>>release 'toaster_1_3' and laster marked as having been fixed in
>>'toaster_1_7'. Not by coincidence, these would correspond to release
>>tags in CVS.


John Minnihan

reply via email to

[Prev in Thread] Current Thread [Next in Thread]