Versions and compatibility
One number, three parts
Section titled “One number, three parts”A version is written X.Y.Z (for example 2.0.20) and is never reused:
| Part that goes up | What it announces |
|---|---|
Z |
a fix |
Y |
a new feature |
X |
a breaking change |
The venue server and the register application carry the same number: a 2.0.20 register is the one that goes with a 2.0.20 server. The installed version can be read in the back office, Paramètres (Settings) → Mises à jour (Updates) (“serveur en …” — server on …), and in the register’s status bar.
Three rules
Section titled “Three rules”1. The platform first
Section titled “1. The platform first”The online platform is always at least as recent as the venues. It never announces or publishes a venue version more recent than itself, and a version can require a minimum platform. For a venue, this requires nothing: the publisher updates the platform before publishing.
2. Never an older version
Section titled “2. Never an older version”A venue never moves down a version through an update: it is only offered versions more recent than its own. Nor does a register: it refuses a version that is not more recent than its own. The only way back is automatic: the previous version is put back if the new one fails its checks (server), or does not start (register PC).
A faulty version is therefore fixed by a following version, never by going back by hand. Same rule for a backup: you do not restore a backup made by a version more recent than the one installed.
3. A register one version behind works
Section titled “3. A register one version behind works”A server on version N accepts registers on version N−1. A server update at night therefore never makes a register that stayed open unusable: it updates later, out of service, with one tap.
| The register is… | What happens |
|---|---|
| on the same version as the server | Nothing. |
| older, but accepted | “Nouvelle version de la caisse disponible (…)” (New register version available (…)) — Mettre à jour (Update), when it is not in service. |
| too old for the server | “Cette caisse doit être mise à jour” (This register must be updated) screen: no money action is possible before the update. Your session stays on the server and resumes afterwards. |
| more recent than the server | “Le serveur de la salle est plus ancien que cette caisse : il se met à jour.” (The venue server is older than this register: it is updating.) The register waits for the server instead of failing in the middle of an operation. |
See Register updates.
The venue and the platform
Section titled “The venue and the platform”A venue too old for the platform sees it in the back office: badge Version trop ancienne (Version too old), with the sentence “Version trop ancienne pour la plateforme : mettez à jour vers … (les envois attendent).” (Version too old for the platform: update to … (uploads are waiting).) The venue keeps working on its own; only its uploads to the platform wait for the update. Nothing is lost.