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

[Brett Cannon]

On Mon, Mar 23, 2009 at 19:21, R. David Murray <rdmurray at bitdance.com>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.
>
> 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).
>
> But am I correct?  And even if I am, this should be documented.
>

Yep, you are correct.


>
> Should I take a stab at it, or does someone better qualified prefer to
> do it? :)
>
> 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?


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.

-Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090324/d2224cd9/attachment-0001.htm>