[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Issue tracker in subversion

From: Gregoire Welraeds <gregoire.welraeds_at_side-international.com>
Date: Tue, 14 Apr 2009 15:48:38 +0200

On 14/04/2009 14:33, Les Mikesell wrote:
> Gregoire Welraeds wrote:
>> Thanks for your answers. Nevertheless, I'm not looking for yet
>> another bug tracker which can interact with subversion by post-commit
>> hooks.
>> I'm looking for subversion hosted bug tracker. That is why I
>> mentioned DITrack and subissue in my previous post.
>> I have the feeling that this 2 projects are stalled.
> Why do you want to use a tool for something it doesn't do well?
For a few reasons, among others:
- Change Requests/issues are tightly related to the code source. IMO,
they could even be part of the code, like comments and documentation
are. Change request could be stored directly in Subversion repository,
next to the source.
- It could enforce teams to work with an issues tracker. To some extend,
Subversion commits comments are just an extension of a Change Request
- Subversion is very good at manipulating text files and their
modifications. Why should I use something else?
- There should be no need to setup additional infrastructure for basic
needs of issue tracking. Why should I be using a third party software
for something which is part of my code, especially if it is bundled with
a third party database.
- It would let me work while being offline. Once online: svn update . /
svn commit . to import my modifications to the issue tracker.
- a tight integration of an issue tracker in subversion would let us
benefits from the inherent features of the VCS and stronger the
interaction between the two. For instance, I could branch my Change
Request tree while creating a feature branch in the code. I could easily
filter the changes requests by branches, be it maintenance, development,
feature branches without having to artificially created the same in an
external third tool.

As a release manager with a team of 10 developers using Seapine
TestTrack Pro*, I always end up to look at svn logs to document the
release. These are only thoughts but I'm sure there are other advantages
of having both VCS and Issue tracker integrated. BTW, the idea is not
mine: see subissue, DITrack or even Fossil scm.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-14 15:49:30 CEST

This is an archived mail posted to the Subversion Users mailing list.