On 15/06/2007, at 9:27 PM, Kenney Westerhof wrote:
When I find an issue that's rather complex I usually describe
how to reproduce it, but I lack the time to write sample projects, at
least when reporting. When i get around to it I reproduce the issue
and fix
it in svn - I normally don't attach tests since I can commit in
core, and i think
that goes for more developers.
If we're fixing it immediately - sure, because the sample goes into
the tests. But if not, I think we need to hold ourselves to the same
standards since sometimes they sit there for a year or two and you
have no idea what they meant :)
Anyway, the incomplete resolution is fine, but closing them will
make them rather hard to find back. Maybe we could just assign
these issues to the
reporters instead, status to 'feedback' or 'incomplete', 'on hold'
or whatever.
Absolutely agree. We can't assign to user under the current set up
(though maybe allowing assign to anyone is a good idea), but I think
an addition of "need info" to the workflow is a good idea.
In the future I'll try to attach the tests as I create the issue,
though that'll
take me 30 mins more and when I'm in time pressure I feel it's
better to report
the issue so it doesn't slip my mind, than to not do it at all
because of the high
overhead.
Maybe assign it to yourself to either finish reporting or finish fixing?
wdyt?
Seems to make sense.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
