Ok, so I've been thinking about how to implement this in a reliable way.
And there are some problems here. See my comments below.
Ivan-Assen Ivanov wrote:
> 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
Here's the first glitch: the commit dialog already is cluttered with UI
elements (and all of them are needed!). Adding another would make things
only worse. And right now I don't know where that ComboBox should go.
> 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.)
The bugtraq: props allow to specify multiple issue numbers in one
commit. So how should we handle that case? Add the same status to all
issues? But then you couldn't close one issue and still assing the
commit to another issue (e.g. Fixes issue 888, brings issue 456 one step
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Jan 5 19:29:17 2005