we do not see anymore the comment on the release list.
it was helpful to have a small remiinder of difference between versions

Add raspberry pi support to Octopus and Calamari.
Self-contained version of Calamari is perfect, but it's not possible to use it on RaspberryPi, because Octopus supports now linux-x64 platform and Pi requires linux-arm.

While typing in the value of a sensitive variable, the complete value is always visible while typing it in.

It would be more secure if there is an option to obfuscate the value while typing it in.

octo.exe is a great tool that wraps much of the Octopus Deploy API. It would be great if we could specify a parameter --output-format=json or --output-format=xml to have octo.exe generate its results in a machine-readable format for further scripting (e.g. in an environment where I have an older version of Powershell without access to modules such as Octoposh).

The Certificate Management feature currently allows uploading certificate chains in PFX files only.

Please also support uploading chains in PEM format.

It would be nice to be able to add notes or an alert to tenants so that we have some warning about release windows or contact people against a tenant.

Allow C# and F# scripts to include references to NuGet packages that are downloaded and referenced before the script is run (see http://scriptcs.net/).

Preferably the feed could be any defined feed and not just NuGet.org.

as an admin, i'd like to receive email notification of failed tasks such as health checks or other automated tasks.

It would be nice to have the option to run different steps based on the status of the previous step (failed or completed successfully). Sort of like an If/Else statement. This way, you can roll back changes if a certain step fails within the deployment process.

PowerShell debugging feature uses special variable Octopus.Action.PowerShell.DebugMode which only allows to turn script debugging on and off. Any real deployment contains many steps and many scripts, out of which only one particular script is under debugging, not all of them.
I propose to make DebugMode selective.
One way to achieve it would be to use special variable to configure step name (or a list of step names) where scripts run in debug mode.
Another way (may be combined with the first) is to let PowerShell scripts to invoke debug break explicitly, exactly where and when it is needed.

Include the time the deployment was made on the dashboard

Source: http://help.octopusdeploy.com/discussions/questions/8580

And please leave a support or contact form so that we can reach out to you with non-technical questions also.

The SAVE button is in the bottom left on the deploy process config page and upper right for the variables page.

When you got a lot of microservices inside a group, one click to start deployment for all of them in their defaults lifecycle

Add a simple summary to the license screen showing how many projects / users / deployment targets are "used" to make it easier to see how much capacity is left in the license and where the capacity is used.

I know you are based in Australia, but if there is any way to have some limited support hours in the USA time zones, that would be extremely helpful. It's kind of rough only being able to get maybe one interaction per day with the time zones what they are.