Application update policy

We release updates of applications to bring you new features (or improve existing ones) and correct defects or anomalies.

Application versions

Each application is identified by a name and a version number. The version number is made up of 4 groups of digits in the form VV.vv.rr.bb where :

  • VV is the major version of the application.
  • vv is the minor version of the application.
  • rr is a revision indicator.
  • bb is an application build indicator.

Version number evolution

The version number evolves with each update according to the following rules:

  • Major version changes are linked to major modifications to the application that could lead to a break in compatibility with the previous version.
  • Minor version changes are linked to the addition of new functionalities in a backward-compatible manner.
  • Revision changes are related to bug fixes that are also backwards compatible.
  • build number changes are linked to modifications to the application distribution medium (installer) and its documentation.

Backward compatible” means that the application can be run on the previous version.

Version release

Improvements and corrections are grouped together in an update which is published with a new version number. We publish these updates as soon as we deem it necessary. The version published on the site is always the latest official version of the application, i.e. the version marketed on the day the site is consulted.

Maintenance and support of the official version

From the date of publication on our site, the published version becomes the official version of the application.

Maintenance of previous versions

The official version is the only one marketed and the only one for which we provide support. We do not provide patches or upgrades to previous versions. If you encounter a problem that prevents you from installing and using a new version, please contact our support team.

Download versions

Download official version

Unless otherwise stated, the official version is the only downloadable version. We do not allow the download of versions prior to the official version.

You can download the official version of an application :

  • when you first acquire a license to use the application,
  • then when new versions (updates) are released.

You can download new versions (or updates) of an application within the following limits:

  • the update must be published as a minor version of the major version licensed to you.
  • the item concerned must not have been the subject of a refund request.

Downloading can be done from your account on this site or directly from the application using the “search for a new version”.

Download “beta version

We may release a version (called “beta version”) of an application before its official publication – and this – in order to allow users who so wish to test this “beta version”, under the terms and conditions laid down in this case.

Download patches

With a few exceptions, we do not publish patches outside of releases. If our technical teams deem it necessary to resolve a problem, they will send you a patch with the implementation procedure.

Right to use new versions

Minor version change

Changing the minor version of an application does not change the associated right of use (license). You can use the new version with the same license (and therefore with the same application activation key).

Major version change

Changing the major version of an application breaks retro-compatibility with the previous version. Furthermore, transferring the right to use an application to a new major version is not automatic.

Depending on the application, we can :

  • offer to upgrade to the new version. You then obtain the right to use the new major version, and lose the right to use the previous major version. Changing to a major version is usually billed at a preferential rate.
  • or offer you the option of retaining the use of your current version by acquiring – if you wish – another license for the new major version.

Applying new versions (updates)

The application of a new version must be carried out exclusively by the user, following the process provided by the application publisher.

Process to follow

With few exceptions, the process of updating a version consists of installing the new version using the same locations (directories) as the previously installed version. The installer replaces the updated elements.

It is not necessary to install all previously released versions in order to install the latest version.

Unless specifically instructed, it is not necessary to uninstall an application before installing a new version.

Impact on data and preferences

We ensure that your data and preferences (settings or chosen options) are preserved when installing each new version.

Updating data structure

If a data structure update is required, the database structure will be updated – if necessary – at the first launch of the new version. This update will also take place if you restore data saved with a previous version, or if the application identifies an incompatibility.

Data backup

Even if installing a new version preserves your data, it is advisable to make regular backups of your data, especially before installing a new version.

Limitations

We make every effort to ensure that any new version can be installed in place of another version without causing data loss or technical problems. However, we cannot guarantee that a technical problem will not occur during this operation, particularly when updating the data structure. The user must take the usual precautions, and in particular back up his or her data before updating the application.

Installation of an earlier version is strongly discouraged. It is not always possible to restore the data structure used by the previous version. If you need to return to a previous version, please contact our support team.