Releases
What a Release number means, where to see which Release a site runs, and the notes of each Release
A Release of aWhere means the whole platform. Every image of a Release is built from the same code and carries the same tag, vX.Y.Z. This section has one notes page per Release.
What the number means
- Z goes up for bug fixes. While the major Release stays the same, you can skip any number of them.
- Y goes up for new features.
- X is the major Release. It goes up when that Release drops old Migrations. To upgrade across a major Release, first upgrade to the last Release of the old major Release (Upgrade stops).
- A test build before the real one has a name after the number, such as
5.1.0-rc.1. An image that did not come from a published Release shows its Release asdev.
You can always roll back to the previous Release, unless the notes of that Release say you cannot (Roll back).
Which Release a site runs
You can see it in three places.
- The System page in Configuration shows the Release of every node (System).
- The command
awhere status. - The file
/etc/awhere/release, which holds the latest Release that was deployed (Upgrade).
If an open page is from a different Release than the platform, every app shows the message "This page is from release X; the platform is now release Y.".
A manual for each Release
The Help button in an app opens the manual of the Release that app runs (Get started).
| Release | Status |
|---|---|
| 5.0.0 | The first Release after v4. A draft until it is published. |
What a notes page has
Each page tells app users, administrators and installers what is new, the breaking changes with what to do about them, and the known issues. If a Release has a contract Migration, its notes say so, because to roll back past that Release you must restore from a backup.