On 5/24/2011 10:41 AM, Kevin A. McGrail wrote:
I don't know if 3.2 releases will be done but the code is committed in the 3.2 branch for this bug. So from a code standpoint, it's resolved.
I continue to be against considering it fixed in Bugzilla because it is upsetting to users if it isn't pushed live.
How about a compromise? Add a new semi-closed state to Bugzilla like PENDING_RELEASE to denote that it is 'fixed' but it isn't pushed to users yet.
But then again, if we really have no intention of pushing a new 3.2 rule update, then this should be closed as WONTFIX to denote reality.
Warren Togami [email protected]
