[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: Bolstridge, Andrew <andy.bolstridge_at_intergraph.com>
Date: Wed, 15 Apr 2009 10:03:28 +0100

From: Mike Meyer [mailto:mmeyer_at_lexmark.com]
Sent: Tuesday, April 14, 2009 5:33 PM
To: Les Mikesell
Cc: vishwajeet singh; Gregoire Welraeds; Jim Hanley;
Subject: Re: Issue tracker in subversion


Les Mikesell <lesmikesell_at_gmail.com> wrote on 04/14/2009 11:28:20 AM:
> I sort-of disagree. Change requests are almost by definition, not
> any version of the code is - and often not even related to anything
> exists. They are generally made by people who don't work directly
> the code, don't have the subversion tools, and want a form/database
> of interaction. That is, they want to count instances of completed
> unfinished requests or find a keyword, not look at yesterday's or last

> week's list of requests or compare two lists.

Right - change requests are related to changelists, not source. The
developers tend to want to ask questions like "Tell me what change
requests this changelist was in response to" and the converse "which
changelist(s) fixed this issue".

> Some trackers have ways to tie the commit revision to the request/bug,

> which is all you need.

Yup. But they tend to do it with commit hooks, which some people aren't
comfortable with. I can understand that: to much code in the commit
hooks leads to to likely failures in said code, which


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

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