Part of this YouTrack ticket on UX issues with the current platform updates / platform changelogs: https://tickets.engineyard.com/issue/UI-98
I think it makes sense to talk about new versions of the platform purely as releases (or patch releases) and avoid using the word 'updates' to describe the releases, instead keeping that word to describe the action a user takes to get the releases. An update should be reserved for what you do to a cluster to apply the Engine Yard platform releases.
Release Changelog:
The latest release version of the Engine Yard Platform is 'Ubuntu Precise v0.4.23'.
It is recommended you keep all clusters up to date with the latest release.
Ubuntu Precise v0.4.23
Ubuntu Precise v0.4.22
Ubuntu Precise v0.4.21
Ubuntu Precise v0.4.20
...
Cluster Update:
- Remove server
- Add/remove any pending changes to IP Addresses
- Apply cluster configuration updates
- Apply Engine Yard Platform release
platform updates -> Engine Yard Platform releases
platform releases -> Engine Yard Platform releases
updates are available for this cluster -> there are new Engine Yard Platform releases to be applied[...]
latest patch updates for our platform -> latest Engine Yard Platform patch releases
4 patch releases -> 4 pending Engine Yard platform patch releases
^ Rough idea. I'll ping product and see what they think, I know similar debates have been held before about what is a platform release or upgrade vs a patch release or upgrade, but I feel like this is a different issue.