As you know, we've been moving toward using Github Issues more and
more. One of the gaps in their feature set is inability to set
alternative resolutions for bugs... they're either "Open" or "Closed",
so you can't tell if they were closed because they're fixed,
duplicate, invalid, or what.
Tom and I want to improve the quality of release management, so going
forward we now have two new milestones: Invalid and Won't Fix.
Invalid: bugs that are not bugs, third-party issues, environmental
problems on user's machine, user mistakes, or duplicates.
Won't Fix: bugs that we recognize as issues or incompatibility, but
won't or can't fix for whatever reason.
Release milestones: bugs that are actually fixed (something was
committed for them) during a given release cycle.
ALL bugs that are closed should have a milestone set. I've marked all
bugs from before the 1.7.5 dev cycle with an amorphous "Pre-1.7.5"
milestone just to clear them out.
Every issue that gets closed in the future should either have a
release milestone (if fixed) or one of Invalid and Won't Fix.
Thanks for your cooperation :-)
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
