[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [TSVN] Trac/bugtraq - Ticket to Changeset link [was: Re: Trac [was: TortoiseSVN 1.1.1 released]]

From: Lars Klose <lars.klose_at_klst.com>
Date: 2004-10-27 21:33:38 CEST

Funny thing: I share Mark's thoughts about wanting to enforce usage of
issue IDs, still I share Stefan's thoughts about not enforcing it in the
Client GUI ... do I have a shizophrenic episode?!? :-O

SteveKing wrote:
> Mark Phippard wrote:

>> If I as the Administrator have to go out of my way to turn this
>> feature on in the first place, by setting the properties in my
>> repository, then why can't you just honor that? You seem to have made
>> up your mind that bug ID's should never be mandatory and I do not
>> really understand why. There are plenty of corporations out there
>> that will absolutely want every transaction to have an ID associated.

Exactly what I would want (most of the time ;-)

> - enforcing to enter a 'valid' bug-ID (tell me: what's a valid ID for
> you?) prevents commits which correct a spelling error, fix some
> intendation, add a more clear comment to a function, ...

In the real world we now have a system (not SVN-based) where you simply
_cannot_ check in anything without having an "issue" (these are actually
distinguished into defects and features). Even reworks of comments are
tracked that way - they are "features"!

Especially being that paranoid, with svn I need to validate on the
server-side if I want to be absolutely safe. This is where Stefan's
comment fits in:

> - As an Administrator, you might have noticed that as soon as you
> enforce whatever restriction/policy, users first get angry (because
> they can't do what they're used to anymore), then they start looking
> for other ways to do what they're used to. And you might have noticed
> how creative people can get when it comes to work around a
> restriction.

I would even go so far that my pre-commit hook wouldn't allow to modify
the bugtraq properties once they are in place! This way getting rid of
another point Stefan mentioned:

> we're talking here about file/folder properties, not
> revision properties. That means that a user can simple remove those from
> his working copy and then commit without the restriction, also removing
> the properties for all other users while doing the commit.

> - What prevents a user from simply choosing a 'valid' bug-ID for a
> commit, even though the commit has nothing to do with the bug-ID? Yes,
> exactly: nothing! So you'll end up with a messed up bugtracker.

That is the one thing you can never be safe of - OTOH it's a mainly a
matter of attitude. Once you're used to it, you simply accept it and
open a ticket even for a small non-functional change. Believe me: after
some time I really _like_ to work that way! (call me a pervert only
silently!) It's all about tracking reasons for changes, probably we
simply shouldn't call those system "bug trackers" - bugs are only one
reason for a change out of many.

For comments on the TSVN side of the whole thing see the next post... ;-)


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Oct 27 22:37:54 2004

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.