Given some mishaps introduced in 3.8.x, we have decided to take a more conservative approach to upgrading Octopus Server.
The current rationale is -1m old from the most current release. See: https://octopus.com/downloads/previous
While navigating the change logs – https://octopus.com/downloads/compare?from=3.14.15926&to=3.12.8 – it’s not very clear when to pick “newer” releases because a previous release introduced serious or breaking changes.
Would it be feasible for Octopus Deploy to denote “Stable” releases (e.g. 3.14.10) as they’ve backed in the wild for some time and based on customer feedback?
We do have a suite of integration and test projects to try to spot functionality regressions – so we’re talking more about server-side issues / unexpected changes. Breaking Changes seems to generally be used for intentional behavior changes.