Updater

This page is about the Updater - the in-program mechanism(s) by which we notify users about updates to LibreOffice and offer to download new versions.

Limitations
Unlike other programs like Firefox, we do not have a fully-integrated "auto-updater" that can download and install a new version of LibreOffice for a user.

Current functionality:
 * Automatically check for new versions on the update server
 * (Optionally) download new versions to a specified directory

Backend
The updater works in a pretty straightforward way.

It is a single .php file that has the git-hashes of the released builds and uses simple logic to decide
 * when to upgrade to the next micro version, and
 * when to update to the next minor one.

Input
The php code parses the passed-in User-Agent string to extract the language, the platform and the LibreOffice version number.

Stored data
Each release of LibreOffice is stored internally in an array that maps a build-hash to a human-readable version.

Note: for some reason, the build-hashes appears to have been cut by 1 letter

A second array stores the current versions for the two active codelines: stable and latest.

(TODO: All of this data should live in a text file outside of the PHP file...) -- it's probably faster to have that Array stored inside the PHP file..

Upgrade Logic
(The comments in the code are confusing...here's my understanding)

If the micro version number of the update is the same or larger than current one, then the latest version is offered, otherwise the stable version.

Hint: The "micro" version number is the 3rd degree of the version number: MAJOR.minor. micro (e.g. 3.5.4)

Let's use some concrete examples to provide clarity. Read this table row by row, e.g.

If the user is running 3.5.2 and the latest version is 3.5.3, then the updater will suggest 3.5.3.

Git repository
The file is maintained in git repo: https://cgit.freedesktop.org/libreoffice/website/tree/check.php?h=update

Improvements

 * We could integrate (and WinSparkle), which is used by many other projects, so its UI and workflow is familiar to users. —Fitoschido (talk) 2014-09-16T11:30:51 (UTC)

Testing
How developers can test the updater:
 * Test Update Check

User Documentation

 * How to Check for Updates (manually or automatically)
 * Options for Online Update