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

["Martin v. Löwis"]

>> Any version it is known to be broken in. So if it was reported in 2.5 and it
>> still broken in trunk then 2.5, 2.6, and 2.7 should all be flagged. It lets
>> people who are using old versions find out what they might have to watch out
>> for since we are not about to fix anything for 2.5 that is not
>> security-related.
> 
> Oopsie, I've applied a different rule to a couple of hundred of issues :)

So do I: I only tag the versions where the bug should be fixed, or, more
precisely, where there is still action needed.

So I remove a version from the list if the bug exists in that versions, 
but will not be fixed there, and also remove a version if a patch has
been applied to that version, but still needs to be applied to other
versions.

> I'll use this rule from now on and eventually fix the wrong changes.
> IIRC, my wrong interpretation is somewhat widespread, so it might be
> interesting to add help/descriptions to the versions input.

Don't switch so easily. I like my rule better than Brett's - what's
your rule?

Regards,
Martin