Mark Phippard wrote:
> Granted. You would also want to use a hook if you wanted this validation
> to be 100%. I am simply trying to spec out something that would be as
> user-friendly as possible. I think that by allowing a feature to exist in
> the UI it provides more opportunity to provide a robust user experience.
> The pre-commit hook happens pretty late in the process and forces the user
> to start over.
I think the features we're discussing here should be very cautiously
separated into features that provide and force the integrated use of a
bug tracking system at a basic level and others that deliver a
convenient user interface for this integration.
The first group should work independently of a specific svn client, and
on the server side. With Trac this basically works well and is achieved
through pre-commit and post-commit hooks.
The user's experience could be better though because he is forced to
remember ticket numbers and enter them in a specific format into the
commit message.
This leads to the second group of features (and to the reason for my
first posting): giving the user as little headaches as possible when
forced to use the bug tracking system is the *svn client's* job, e.g.
TSVN's.
Having things separated like this may lead to much better acceptance of
the whole concept. I could still use some non-bugtraq-enabled svn client
when needed (IDE-integration comes to mind!) without risking to break
the integration. And if needed you could add bugtraq support in a
similar way to any other svn client than TSVN.
It all boils down to a well-defined interface between svn, svn clients
and issue tracking systems.
Lars.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Oct 27 17:57:42 2004