I agree with Vlad in that whatever solution we develop, it definitely
should not be dependent upon a single client interface.
Ronny and I have spoken a bit via email about this topic. As an
example, TortoiseSVN already handles some degree of issue tracking, when
the issue tracking is done via a set of rules they've set forth. While
TortoiseSVN is significant, and perhaps one of the most popular clients
for Subversion, I still think Vlad is right...the issue tracking should
not be limited to a single interface.
However, I'm not sure that extends to administration of the
issue-tracking system. If the administrative interface to 'subissue' is
web-based, but various clients can interact via some issue-tracking API,
with all the metadata stored within the subversion repository itself,
then, to my mind, that's a clean solution. You may disagree.
If you haven't seen the spec the TSVN guys have laid out, here's a link:
http://tortoisesvn.sourceforge.net/docs/release/TortoiseSVN_en/ch05s24.htmlIf nothing else, perhaps this will give us some solid grist for the mill
:).
drew
--
Never offend people with style when you can offend them with substance.
- Sam Brown, Washington Post, 1977
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...
For additional commands, e-mail:
dev-help@...