Currently if you setup a retention policy to be based off 3 items, it will delete folders past the 3 items back. In our scenerio we have version numbers in our Nuget packages and in Octopus of WCF services that are hosted in IIS. We found that when Octopus retention policy ends up deleting a folder that is being pointed to by IIS that IIS will then just fails to load the application pool and crash everything else in that same application pool. To address this, can the retention policy be enhanced to support versioning and especially in relation to the tentacle policy? All of our release numbers are in format .... so for example say you already had these releases:
let say 188.8.131.52 gets released. if we based retention policy on major/ minor version, then 184.108.40.206 and 220.127.116.11 would get deleted if we assume we wanted to keep 3 items for each major/minor version. Which parts of the version number are used to determine what retention is based on could be configurable.