[development] Policy for setting issues to 'fixed'

Arancaytar arancaytar.ilyaran at gmail.com
Tue Nov 18 19:30:56 UTC 2008

Maybe an extra state around the words of "Fix Released"? "Fixed" would
be renamed to something like "Fix Committed", and only "Fix Released"
would be auto-closed?

I've had no problems as a contrib maintainer convincing users that they
just needed to wait for the release. But I also admit that I release
fixes for non-trivial bugs on a quick schedule of only a few days after
the initial commit if no other problems are reported.


On 18.11.2008 20:23, Nathaniel Catchpole wrote:
> 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.
> Nat

Nothing beside remains. Round the decay
Of that colossal wreck, boundless and bare,
The lone and level sands stretch far away.
AOL:  realarancaytar / 282026638
XMPP: arancaytar.ilyaran at gmail.com
PGP:  http://ermarian.net/downloads/0x27CA5C74

More information about the development mailing list