Retention Policy: Currently deployed releases

Currently we can configure retention policies for releases that have never been deployed and releases that have ever been deployed. For us a more useful policy would be to be able to configure things differently for releases that are currently deployed. For example, if version 1.1 is in Production and 1.10 is in development I would like to keep release 1.1 around indefinitely even though I may want to delete releases 1.2-1.9 based on their age.

Also, because our releases are automatically created and deployed to by our CI server the two existing policies are functionally equivalent.

Hi Trevor,

That’s a really interesting suggestion, thanks. We’ll consider it for Octopus 2.0.