Hotfixes are limited collections of updated product files and may contain binaries as well as other files. The hotfix packages from BoKS version 6.6 and later use the following naming scheme:
ID - Hotfix ID. A number from the range 0001-9999.
VER - Version. An incremental number 1,2,3...
The first release of a hotfix starts with version number 1.
The version number is included in the package name, in the README file
and is also recorded in the BoKS ENV file when the hotfix is installed.
REV - Revision. A letter A,B,C...
The first release of each version of a hotfix does not have a revision letter.
The revision is only visible in package names and in the README file.
When the version number is incremented some of the files in the new package are replaced by updated or corrected versions. A new version of a hotfix completely replaces all previous versions and revisions of that hotfix.
A new revision of a hotfix complements the platform support for that hotfix but does not replace any of the files for existing platforms.
How the version and revision change when a hotfix is updated
- If the update is a functional change of the hotfix (bug fix etc.), then the version number is incremented and any revision letter is dropped.
- If the update is only adding support for new platforms, then a new revision of the hotfix is built and a revision letter is added to the name. The only change to the hotfix package is the new platform support. The binaries for the original platforms are left untouched.
Example of hotfix release history:
1. HFBM-0001-1 Initial release
2. HFBM-0001-1-A Added new platform
3. HFBM-0001-1-B Added new platform
4. HFBM-0001-2 Bug fix
You only need to upgrade installations of the previous hotfix version when the hotfix version number is changed.
The hotfix README file has a HOTFIX REVISION HISTORY section that contains a complete history of the changes for each new release of the hotfix.
Adding support for a new platform to an existing hotfix
This usually occurs when a port to a new platform is made between patch releases. The base package is built from the same source code branch as the last patch release. All hotfixes released after the last patch release are then updated with support for the new platform.
Still have questions? We can help. Submit a case to Technical Support.