SteveKing <steveking@gmx.ch> wrote on 08/22/2004 05:28:56 AM:
> Mark Phippard wrote:
>
>
> As you already mention yourself: you can get around that restrictions
> with the command line client.
Correct, and if you will not put this in the UI as an option, then the
user has to write a commit hook which would be more complicated and less
flexible since there would be no way around it.
>
> I'm not insisting that I'm right on this point. All I'm saying is that
> I'm the one who will have to deal with angry users, not you.
I am not buying this. First, the feature has to be turned on
specifically. Second the overwhelming place it would be used is a
corporate environment where TSVN was provided to the user by the company.
I find it hard to believe they are going to complain to you. Even if they
did, there is a very simple answer and explanation. Why is it that you do
not care about the people that might want this feature and have no real
way to enable it themselves? The people that do not want the feature can
always turn the feature off. Heck, since this is a folder property, they
can even do it themselves.
>
> Even if I would implement such a feature, it wouldn't take long before
> users start working around it. First, there are always changes which are
> never assigned to an issue, e.g. gramar/spelling fixes in comments.
> Second: TSVN and any other client have no way to know if the issue
> number entered is even valid! That means users will soon find out about
> that and just enter some bogus issue number to get around that
> restriction. Even if you then decide to use a pre-commit-hook to only
> allow valid issue numbers, users will then just use any existing issue
> number they find - even if the commit has nothing to do with it.
> So the point is: all those "workarounds" users _will_ do will do more
> harm than just entering no issue number at all.
> And last but not least: once users find out that other clients don't
> bother them with that feature, they will say that TSVN is crap and use
> another client instead.
>
I do not buy any of this. People that go out of their way to enable this
feature will want it. We are building a system on a house of cards as it
is since we are relying on a perfectly formatted log message for the
features to work properly. Right now, if a well intentioned user forgets
to enter the bug ID, adding it in later is not trivial and cannot even be
done from the TSVN UI. It also would require a hook script be enabled to
allow the log message to be edited after the fact.
As for your other items, people that want every commit to have a valid
issue ID will have to use a hook to validate it. There will never be a
way around that. However, I think there is a middle ground where you want
95% of your commits to have issue ID's and you do not care if someone has
a catchall issue ID, or special issue ID for the rest. In this case, the
property is a UI feature that makes the product easier to use since you do
not forget to specify an ID. And again, you can always just not enable
the feature in the first place since it is off by default.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Aug 22 17:33:39 2004