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

[TSVN] bugtraq enhancement proposal: changing bug status

From: Ivan-Assen Ivanov <ivanassen_at_gmail.com>
Date: 2005-01-03 01:22:48 CET

Hi,

after a working a few days with TSVN 1.1.2 I can say I'm spoiled by
the bugtraq integration features. I tied both connections between our
Subversion server (thanks to TSVN's bugtraq properties) and our Mantis
installation (thanks to Mantis' checkin.php script), and now there is
a two-way connection between bugs and commit logs.

But laziness is one of the most powerful forces behind engineering,
and I'm starting to think: why do I have to mark a bug as resolved via
the Mantis web interface right after I enter this bug's number in
TSVN's commit dialog? Why can't I change the bug status directly from
TSVN?

So I'm proposing the following addition to the bugtraq support:

A new property is defined, 'bugtraq:status'. It is a
semicolon-separated list of possible bug resolutions arising from
source code changes. The first of them is the default, which is
something meaning "don't change bug status".
(In the case of Mantis, that property would have the value of "--no
change--;resolved" as all other bug resolutions like "won't fix" or
"unable to fix" or "duplicate of another bug" shouldn't result in
source code edits, and as such don't have a place in a commit dialog).

When such a property is encountered, TSVN displays a combo in the
commit dialog; by default the first option is selected, which would
mean"don't change bug status". If the user chooses one of the other
options, a new line is appended to the commit log, its format commited
by another new property, 'bugtraq:status-message', analogous to the
'bugtraq:message' property. (And of course, the combo-box is preceded
by a text label specified by the 'bugtraq:status-label' property.)

From there on, it's all the responsibility of the bug tracking system
itself: some part of it should be invoked by the post-commit hook, and
it should parse this message and modify its database appropriately.
I'll probably enhance Mantis' checkin.php myself and submit it there -
their developers seem to be keen on assisting version control
integration.

I realize this might not fit everyone's established workflow, but it
perfectly fits ours - when bugs are fixed with code, the programmer in
most cases writes no specific comment on the bug, just marks it as
resolved. Any comments go into the commit log (and before TSVN 1.1.2,
we didn't even tie this to the bugtracker itself.)

What do you think?

Regards,
Assen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Jan 3 01:23:42 2005

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