[Tracker-discuss] type field, specifically 'crash', and proper setting of 'versions'

[Daniel (ajax) Diniz]

OR. David Murray wrote:
> The workflow document explains the stages, but doesn't cover types.
> I think it would be useful if there were some definitions and examples.

Agreed, and we can add tooltips to the UI later on.

> This came up because I reviewed issue 2259.  The submitter set it to
> 'crash', which I would imagine actually refers to the interpreter
> crashing.  So I changed it to 'behavior', which I imagine means "things
> are behaving according to the docs" (ie: this is a bug).

"things are not behaving...", I guess. That's exactly the way I
understand 'behavior'.

> But am I correct?  And even if I am, this should be documented.

Not sure whether you're correct, but if you're wrong I can tell you
I've made the same mistake in 98% of the issues I've updated so far.
So I hope you're right :)

> Should I take a stab at it, or does someone better qualified prefer to
> do it? :)

Unless Brett or Tennessee have this already written, I say go on, please!

> Also, what "should" be selected in the versions field?  All versions in
> which the bug appears?  Only versions in which the bug might get
> fixed?  The version in which it was reported plus any later versions
> in which it is still broken?

I'm using the 'versions the bug might get fixed' target (RFEs set to
next major release, bugs and doc RFEs for minor releases), but have
the same doubts. Thanks a lot for bringing this up!

Cheers,
Daniel