Mark wrote:
> Why not just try to support more usage models?
> Finally, as that other poster pointed out a few days ago,
> there might be admins that want absolutely everything to
> have a bug ID associated with it, even basic repository admin tasks.
IMHO it's because adding features has a cost associated with it, namely
complexity. As software designers, sometimes we really *do* know better
than users. Although that may sound condescending, I honestly don't think
allowing admins to *force* users to input a bug id is a good idea. It will
force people to work around the restriction. Out of control admins
shouldn't be given the ammo to be able to subject their devs to crazy
requirements. If they need to force devs to do that, it should be a policy,
not a mandate provided by the software because there are always exceptions.
Generally, I don't agree with the idea of "why not just add a switch to
support every possible mode?" because then you end up with unusable
software. If adding features is expanding the usage of the tool, then
that's wonderful, but if it's because the developer couldn't decide the
answer to a question (in this case 'should bug id's be mandatory?') then
it's not so wonderful.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Aug 22 13:23:22 2004