24. Add a "release_status" field Proposal:
Add a mandatory ''release_status'' field with a limited list of acceptable values. E.g. "stable", "testing" and "unstable", with "alpha" as an alias for "unstable" and "beta" as an alias for "testing". Have PAUSE use this field first to determine whether distributions should be indexed. (Eventually, have PAUSE create separate indexes "stable", "stable+testing", "stable+testing+unstable".) Comments: * This is more useful than the boolean 'development version' proposal as different authors use development versions for both testing and unstable. In response to Adam's concern about knowing status post-installation, see the proposal to install Meta files and make them queryable. (Dagolden) * Should "release candidate" be an allowed value? Should it be an alias for "testing" or should it exist on its own? (Dagolden) * "release candidate" is mostly just a hint to humans that this is your last chance for testing... I don't see any difference in behaviour for consumers at this point --Adam K
