Skip to content

Pre-releases

A pre-release is a release candidate of the next version of Scalio Pulse that Scalio opens to customers before the release, for testing. You only get pre-releases if you switch on Show pre-releases. Without the switch, Pulse offers final releases only and nothing changes for you.

For testing, without a way back

An update to a pre-release cannot be undone. The only way back to the old version is restoring the backup made before the update. Support is best effort, without an SLA.

What a pre-release is

  • A pre-release has a version number with rc (release candidate), for example 1.3.0rc2. Scalio opens only release candidates that passed its tests, and not every release candidate becomes a pre-release.
  • The order is 1.3.0rc1 < 1.3.0rc2 < 1.3.0 < 1.3.1rc1. The final release 1.3.0 is offered to an installation on 1.3.0rc2 as a normal update.
  • Pulse marks a pre-release with the badge Pre-release.
  • This manual describes new functions only with the final release. Until then, the release notes of the pre-release describe them (see Release notes).

Show pre-releases

Coming with a later version

The switch comes to Scalio Pulse with one of the next versions. Until then Pulse offers final releases only. This section describes how it works then.

Settings → System → Updates (administrators only) has the switch Show pre-releases. It is off by default and applies to Pulse only; other Scalio apps have their own switch.

  • Switching it on asks for confirmation and lists the consequences: no way back to the old version, only restoring the backup made before the update; best-effort support, no SLA; pre-releases are installed only on your click. The checkbox Send error reports from pre-releases to Scalio in the same dialog is off by default.
  • Switching it off does not ask.
  • Every change of the switch is written to the activity log.

SaaS: Scalio offers a pre-release only to instances with the switch on.

  • The banner and Settings → System → Updates show Pre-release … is available with the badge Pre-release and a warning.
  • A pre-release has no deadline ("no deadline, only on a click"). It never runs on its own, not even in the maintenance window, and Scalio cannot force it. You install it with Update now or on a date you choose; Postpone until is not offered.
  • The owner of the subscription gets an email when a pre-release is available.

Self-hosted: the Scalio Installer reads the switch of each app. It offers a pre-release only for the apps with the switch on and shows the warning before the update.

Backup before the update

A backup before the update to a pre-release is mandatory: it is the only way back.

  • Create an export with Include data under Settings → System → Backup and download it before you click Update now. Keep the file and its password until you are on a final release again.
  • SaaS: in addition, your database is backed up before every update, as for every version.
  • Self-hosted with the Scalio Installer: the installer makes a backup before every update mandatory.

Back to the stable version

  • Switch off Show pre-releases: Pulse gets no new pre-releases. It stays on the installed pre-release until a release at least as new is available, usually the final release of the same version. That release is offered as a normal update.
  • No downgrade: an older version is not offered on a pre-release.
  • Back to the state before the update: restore the backup made before the update (import). Everything changed since the backup is lost.
  • If Scalio withdraws a pre-release, your installation stays on it and gets the next pre-release (with the switch on) or the next release.

Support

  • Pre-releases have best-effort support. The service levels (SLA) of your support do not apply to errors that occur only in a pre-release.
  • Please report problems as usual to Scalio Support and name the version (for example 1.3.0rc2).
  • Final releases keep the normal support terms.

License

  • A pre-release follows the same rule as every update: your license covers it if it covers updates (a valid license with maintenance).
  • The Community edition and trial licenses may also use pre-releases, but without support.

Release notes

  • Every pre-release has release notes. Their title starts with Pre-release and names the version, for example "Pre-release 1.3.0rc2", and they are marked as a pre-release.
  • The offer of the pre-release links its release notes, as for every version.