My 2c....if we add a new status, it should equate to "deployed on the
cluster", along with judicious use of milestone so that people who are
just interested in the tarball can infer from our numbering what the
corresponding release will be.
The more statuses (statii?) we add, the less likely they'll actually
be a source of actual information. That said, I know that many
developers get confused about when they should mark things fixed, and
hold off on doing so because things just get reopened with "hey, it's
still broken for me". I'd like the developers to be able to mark
things off of their list when they're done with them, and the rest of
us to worry about communicating when the fix is actually
released/deployed or is otherwise relevant to them.
Rob