We have two different ways of describing updates for our products.  Both methods involve a "build" number (i.e. 172 or 173), and a "hot fix" number (i.e. HF1 or HF2).  The first method is a Web Sync (WS).  Web Syncs go through formal QA testing before being released, and are put on the supportline site for any customer to download.  They are incrementally named.  The second is called a Hot Fix (HF).  These do not go through formal QA testing and are not put on the supportline site for general download.  Hot Fixes usually address specific problems and are distributed by Support Reps on an as-needed basis.  Hot Fixes are also incrementally named.

All Web Syncs & Hot Fixes have an associated "build" number that development assigns them.  While they are incremental, sometimes a build does not pass rudimentary testing and is discarded.  This is why you may see a "skip" in the build numbers.

All Web Syncs, Hot Fixes, and builds are cumulative.  So build 178 will contain all previous Web Syncs, Hot Fixes, and builds.  There is no need to incrementally apply patches.

In the past, our naming convention was inconsistent.  We have arrived at a standard which breaks down to this:


Product: TestPartner

Version: 6.3 (6.03)

Build: 178

Web Sync base: 2

Hot Fix #: 6

The Web Syncs can be downloaded from Supportline, but Hot Fixes are sent by Support on an as-needed basis since they aren't QA tested.  If you are experiencing an issue, then we will likely send the newest build (Hot Fix) to see if that remedies the problem.  We don't generally recommend applying a patch/build/HotFix if there are no problems.
Incident #2481208