Hi.
I've started to look for an easy way to figure out which release of Octopus Server that can be considered stable, since my colleagues are depending on the software and they aren't pleased the amount of bugs that has been coming and going.

I've been helping out on the community template

http://library.octopusdeploy.com/step-templates/4b3a1f09-1827-41bb-88a4-894c6317922b/actiontemplate-upgrade-octopus-server

which lets the Octopus Server easily do rollbacks, in case of major bugs.

Michael Noonan suggested in this thread
https://help.octopus.com/t/overall-quality-of-octopus-server-updates-are-integration-tests-being-applied-to-octopus-server-upgrades/19214

that some customers uses the latest version of the previous feature release to make sure Octopus is semi stable. I'm very aware that even a stable version might have bugs, but hopefully not as many as the current monthly release.

Currently a new version is retrieved in the step template like so:
https://download.octopusdeploy.com/octopus/Octopus.$versionNumber-x64.msi

If there's an alternative feed like
https://download.octopusdeploy.com/octopus/stable/Octopus.$versionNumber-x64.msi

then both the step template and Octopus Server can check for it (to notify the administrator). In Octopus Server, it would be ideal if the administrator can set a check option for either the 'latest' or 'stable' patch.

Currently the upgrade notification is set to
http://octopus.helsenord.no/app#/configuration/license
where you can choose between 3 options.