Version Release and Status Policies



This Knowledgebase article is one of a series of articles linked to Knowledgebase article #4 - 'Products and Versions', that explain the various releases of Neverfail Heartbeat.

More Information

Versions of Software

Neverfail Heartbeat and SCOPE Data Collector Download version numbers follow the following form: "v5" or "v5.1" or "v5.1.3". In addition, SCOPE Collector versions also follow a similar format to Heartbeat, but are actually an independent range of versions. SCOPE releases are totally independent of Heartbeat Releases. Plug-ins for Neverfail Heartbeat and other software, such as Utilities, have independent version numbers using a similar format to Neverfail Heartbeat for example, "v201.5.1".

Build Strings

Build strings are alternative version numbers used internally to identify the exact software. The build string is embedded in the software kit, so it usually appears in log files to show product installation. Various Knowledgebase articles show the one-for-one correspondence of the build strings and the version numbers for our software. For example, Knowledgebase article #529 - 'Versions of Neverfail Heartbeat' shows the build numbers for all the Heartbeat versions.

The following table shows the format of versions and build strings:

Version Number Format

Build string Format


[Vn.n] or [Vn.n.n]

Example: v5.0.1

[Vn.n] or [vn.n.n] - [nnnn]

Exmaple: v6.2-6834



Example:  v201.5.1

[v nnn.n.n]-[nnnn]

Example: v201.5.1-5529

SCOPE Collector

[Vn.n] or [Vn.n.n]

Example: v5.1.2

[Vn.n] or [Vn.n.n]-[nnnn]

Example: v5.0.1-1054

SCOPE Analyzer (a service on the Neverfail Extranet)


<A 4-digit number beginning with 1>

Example: 1042

Heartbeat Log Collector Utility


Example: 1.17.13


DNSUpdate Utility

[nn.nn.nn.nn] or [nn.nn.nn]

Example: or 01.04.02


Other Utilities, including:

<!--[if !supportLists]--> · <!--[endif]--> AM(X) Questionnaire

<!--[if !supportLists]--> · <!--[endif]--> AM(X) Developers’ kit

<!--[if !supportLists]--> · <!--[endif]--> Leave Behind Report

<!--[if !supportLists]--> · <!--[endif]--> Heartbeat Server Roles in Registry Utility

<!--[if !supportLists]--> · <!--[endif]--> Exchange Filter discovery utility.

FileMaker Server Create Shadow Utility

UPS AutoSwitchover


E.g. 2006-12-25


Versions of Technical Documentation

Heartbeat and SCOPE technical documentation follow the same version numbers as the software to which it refers. The documentation does not change with major sub-versions -- for example technical documentation for Neverfail Heartbeat V5.0.1 and V5.0.2  will be listed as V5.0. Should there be an error in the technical documentation, the version numbers will change and follow this format -- V5.0-Rev2 or V5.0-Rev3.

Release Status

Items such as software or documentation are available for download on the Extranet. Release status is as follows:

  • Beta - Similar to Preview, but with a planned process of beta testing at partner or customer sites.

  • CURRENT - The version of the software that we suggest people use. Unless you explicitly choose to see other versions, the Extranet will only show you CURRENT items.
  • Superseded - Software that has been replaced by newer software. Superseded software would only be installed in unusual circumstances. For example, you might install superseded software when adding a sister implementation of Neverfail alongside some stable implementations with the same, now superseded version.
  • Obsolete - So old that we can't recommend installation under any circumstances. Obsolete items are not visible to download. See Knowledgebase article #528 - 'Release Status Policy (Partners)' for information for Neverfail Partners.

Separate to the release status is the "No Longer Supported" status - this implied that not only do we not recommend installation, but we also cannot provide the same level of support for this version.

The contents of versions do not change

Once a piece of software is released, the contents of the download do not change. However, the release status may change, from Beta to CURRENT to Superseded to Obsolete. For example, if we released a Beta version of a new plug-in for ABC on December 25 20010, we would version it v201.5.1. If on 15th January 20011 we completed the beta test with no errors found and decided to make it fully live, we would change the status of the v201.5.1-1234 plug-in to CURRENT. On the other hand, if on 15th January we completed the beta test and produced a different piece of software with a bug fixed, we would call this new kit v201.5.1-1235 with status CURRENT; we would then switch the status of the v201.5.1-1234 to Obsolete.

Applies To

All Versions

Related Information



0 out of 0 found this helpful



Please sign in to leave a comment.