Comment 111 for bug 1164016

Revision history for this message
Andrew Simpson (adpsimpson-gmail) wrote :

> Oh I see why: most of us cannot change back the status of the bug once it has been changed to "fix released" (which is stupid, too).

If that is genuinely the reason (and this bug has been marked as "Fix Released" since Jan 2014, so it seems correct), then is it not time to raise a new bug?