Our Release management process would be enhanced by allowing more than Unreleased/Released as the status for a version.

For example, it would be very useful to have a release in state "Development", and then propagate it through "Integration Testing", "System Testing", "User Acceptance Testing" and finally into "Production". Another state, say "Retired" or "Deprecated" would be useful as well.

This needn't be a formal lifecycle/workflow kind of approach.

There is probably an overlap with the Version family ideas discussed in JRA-5316 and JRA-5680.