Mark Phippard wrote:
> These three are irrelevant. The types of users I envision this for would
> never find another client. Even if they did, I think anyone that turned
> on this feature would try to also have some kind of pre-commit hook. This
> is mainly about making the front-end friendlier.
See, that's exactly why I think I should rather just delete your mails
instead of answering them: you just think about _your_ users. But TSVN
has many users, and I have to think about them too. And what's your
point anyway if a pre-commit hook does some checks too?
I mean a warning (as I suggested) would be enough. If then the
pre-commit hook rejects the commit - at least the user was warned about
that. But at least the user wasn't _forced_ to choose some bug-ID which
maybe has nothing to do with the commit.
>>- 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, ... So you'll end
>>up with those corrections mixed into other commits assigned to a bug-ID.
>
>
>>And that's very, very bad from a source control point of view.
>
>
> These are your opinions spilling through. If you have to undergo SOX
> audits or are trying to maintain an ITIL certification, then yes you will
> want to have a bug-ID for these changes.
Don't know what SOX audits or ITIL certifications are. But if they're
similar to some other certifications we have here for companies then I
can guarantee you one thing for sure: you can smoke those
certifications! All they do is add a lot of paperwork and costs, with
_no_ benefits at all. Just as an example: I work in a company where we
survive the audits every time and get the certificate. But we _have_ to
work around the rules to get our work done. If we would actually do what
we claim to do and the certificate requests us to do, we wouldn't get
anywhere and couldn't even deliver our products on time!
>>- 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.
>
>
> Possibly, but at least the tool has helped as much as it reasonably can.
No. Exactly the opposite! If you _force_ the user to enter a bug-ID, the
first thing he will do (after a nice dialog tells him that he has to
enter a valid bug-ID) is to just pick one of the valid ID's and then commit!
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
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:51 2004