Sounds great. I think if the SVN team doesn't want to deal with this or
document it, then we should just go with what we think is best and document
it ourselves. Then if other GUI's want in on the action, they can follow
our lead. Clearly, it would be ideal to have the spec implemented in SVN
core so others could use it too, but I think we have a decent understanding
of the problem and if they don't want to, or don't have the cycles to,
implement this feature set, then that's ok. The integration (bug
tracker->svn) already exists using an SNV hook, I just want to make it more
robust by extending it through TortoiseSVN so we can go back the other way
(svn->bug tracker).
Michael
-----Original Message-----
From: SteveKing [mailto:steveking@gmx.ch]
Sent: Tuesday, August 17, 2004 3:42 PM
To: Mark Phippard; TortoiseSVN Dev
Cc: michael@fogcreek.com
Subject: Re: Integration with Bug Tracking
Great work on the first draft.
I'm forwarding this to the TortoiseSVN dev list for a wider discussion:
(Also cc'ing Michael from FogCreek Software, since he's also working on the
same task and might have ideas on this)
> ----------------------------------------------------------------------
> --
>
>
> Integration of Subversion with Bug Tracking Tools:
>
> This document is primarily intended for writers of various GUI clients
> for Subversion. Clients such as TortoiseSVN, Subclipse, RapidSVN,
> PySVN and many others.
>
> The goal of this document is to outline a common technique for
> defining and then integrating these GUI clients with third party bug
> tracking software.
>
> It is very common in Software Development for changes to be related to
> a specific bug or issue ID. Users of bug tracking systems would like
> to associate the changes they make in Subversion with a specific ID in
> their bug tracking system. There are already a number of people that
> have integrated these systems with Subversion. They typically rely on
> the end user entering a log message on their commits in some kind of a
> specific format that can be parsed with a hook or in some cases just
> on-the-fly in a web-based presentation of the commit info. This
> option is OK, but it is not very user-friendly and it places all of
> the integration within the bug tracking tool.
> When using a Subversion client, you can see the log message info, but
> there is no way to jump to the bug system.
>
<snip>
I think once we got this worked out, we should send this to the Subversion
mailing list and simply _insist_ that this should be implemented. If not in
the Subversion core, then they should at least define the standard and
document it somewhere on their website so that all Subversion clients will
use the same standards. Otherwise, we might end up in chaos.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Aug 18 08:52:25 2004