Ability to retain release indefinitely
We often have the case, where a release has been cleared from QAT, but we continue development on QAT until the deployment date comes along a few days later. As it currently stands, there is no way for us to prevent the lifecycle retention policy from removing that release, once we start deploying the releases from the next sprint to QAT. In other words, unless a release is kept as deployed in an environment, we run the risk of it getting deleted by the retention policy.
It would be extremely helpful to be able to mark a release as "retain indefinitely" or "exclude from retention policies" in order to ensure that those releases are kept until we are able to get them deployed into an environment.