We discussed this change before and I think everyone liked the idea, so I updated the milestones for SpamAssassin:
- default milestone is now "Undefined" instead of "Future" - "Undefined" means not yet having a milestone - "Future" is a new milestone essentially meaning "later, but not resolved". (LATER the state means "later, and resolved" which is a nice way of saying "probably never".) The process change is basically: - new bugs have an "Undefined" milestone until they have been triaged - in triage, a milestone should be set for a specific release or "Future" - all bugs should be triaged from now on The hard one for us will be the last one (especially the many now "Undefined" bugs), but it's time we did it for every bug. We sometimes forget to triage a new bug and I think the distinction between "Undefined" or "Future" will help. Daniel P.S. some incidental changes: - added milestones for 3.1.1 and 3.2.0 - updated sorting keys (-1 is no longer valid for some reason, so I changed them all to 0 and 10 instead of -1 and 0) -- Daniel Quinlan http://www.pathname.com/~quinlan/
