[development] Policy for setting issues to 'fixed'

Nathaniel Catchpole catch56 at googlemail.com
Tue Nov 18 19:23:41 UTC 2008

I agree with Darren on this - by definition, an issue can't be fixed in the
'current' release - because that's frozen, so it will always be fixed in the
next one. And it seems like a lot of unnecessary work to go back marking
issues as fixed when you actually roll a release.

This does bring up an issue I've noticed a lot though - many users re-open
issues which are marked fixed, because the bug is still present in whichever
version of the module they're currently using. Also - if something gets
fixed, and the next version of the module isn't released for some time, then
the 'fixed' issue gets marked closed, drops out of the main issue view, and
results in lots and lots of duplicates being posted because people don't see
it. Would be worth considering ways to make these fixed issues more visible
to those trying to report bugs.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20081118/0d7ed51a/attachment-0001.htm 

More information about the development mailing list