David Weintraub wrote:
> [...]
> This adds an amazing bit of power. In most defect tracking/source
> control integrations, almost all queries must be handled via the
> defect tracking system. For example, if I want to know what files were
> changed by particular defects, I query the defect tracking system. If
> you had Perforce and integrated the job control system into the defect
> tracking system, almost all of your queries could be done directly
> from the source control system. You could generate release notes
> between two Perforce change sets and include all defects that were
> fixed, how they were fixed, and when they were fixed.
well, with subversion, usually, you create a branche to fix a bug, and then,
all commits to this branch have something to do with the bug.
(you can retrive them very easily, import the changes (almost) where you
want, etc.)
In addition, the notion of bug (managed or not by a third party tools)
imply that you specify, with a commit, some information (identification)
about the related
bug. This can be 'commit in a specific branch' (dedicated to the bug),
but more frequently,
you (also) give such identification through the commit log (like: BUG-1234)
With such convention, looking for every commits having "BUG-1234") in
their log message is easy.
> [...]
> Of course, the answer whether Subversion has a ticketing system is
> still "no", but it might be something interesting to consider in
> future revisions of Subversion.
hum... personnaly, I will be really disappointed if subversion will
"offer" such kind of "feature"
(deeply integrated, of course; having a "package" subversion+trac (for
example) is perfectly acceptable)
- my two cents -
regards,
flo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-20 08:26:31 CEST