Jeeva Sarma wrote:
> In our team, one developer wants to make tags for a few
> files; suppose he is working on 2 bugs, each requiring
> changes in 2 or 3 different set of files, he wants to tag
> each of those 2 or 3 files with the bug number, so that he
> can remember which files are modified
The way we approach this in our team is to have a bug tracking database.
When we fix a bug, we put a list of the files that changed in the database.
Then we can query the database by bug number, file, or whatever. It's a
little more work, but more flexible than trying to use CVS for this task.
--
>--- Forwarded mail from [EMAIL PROTECTED]
>Jeeva Sarma wrote:
>> In our team, one developer wants to make tags for a few
>> files; suppose he is working on 2 bugs, each requiring
>> changes in 2 or 3 different set of files, he wants to tag
>> each of those 2 or 3 files with the bug number, so
Indeed. You can even have a *info script update the defect database with
the files and version numbers.
Your database maps files to defect numbers? Which product do you use, if
it's not proprietary?
--- Forwarded mail from [EMAIL PROTECTED]
The way we approach this in our team is to have a bug
D]; [EMAIL PROTECTED]
Subject: RE: Tags usage -- comments please
Indeed. You can even have a *info script update the defect database with
the files and version numbers.
Your database maps files to defect numbers? Which product do you use, if
it's not proprietary?
--- Forwarded mail from [
I agree. In my previous company build process provided report in a format:
bugID/changeID
bug description
developer, who fixed
developer's CVS comments associated with the fix
list of files modified for the bug
This was a very effective way to communicate source changes, because it
provided the c
So there's no relational query (or equivalent) to perform this function?
Bummer. Not many defect tracking systems seem to offer such a capability
without heavy customization, which is unfortunate.
--- Forwarded mail from [EMAIL PROTECTED]
Well, it's not explicitly supported, but we use the comme
On Thu, Jun 10, 2004 at 11:33:51AM -0700, Eugene Kramer wrote:
>I agree. In my previous company build process provided report in a format:
>
>bugID/changeID
>bug description
>developer, who fixed
>developer's CVS comments associated with the fix
>list of files modified for the bug
>
>This was a ver
"Jim.Hyslop" wrote:
>
> Jeeva Sarma wrote:
> > In our team, one developer wants to make tags for a few
> > files; suppose he is working on 2 bugs, each requiring
> > changes in 2 or 3 different set of files, he wants to tag
> > each of those 2 or 3 files with the bug number, so that he
> > can rem
