|Table of Contents|
This document explains the cPanel & WHM version system and release process.
We publish new versions of cPanel DNSONLY™ concurrently with new versions of cPanel & WHM on the same release tier. Hosting providers can update their DNSONLY servers when they update their cPanel & WHM servers.
A cPanel & WHM version number consists of three incremented integer values. Periods (
.) separate each value.
The following table explains these values:
These represent sets of new features. We often refer to the builds within the lifespan of this value as a release.
These represent sets of bug fixes and changes that stabilize the features that we released in major value versions.
|Build value||These represent a unique build of cPanel & WHM.|
As of cPanel & WHM version 54, the user interface no longer includes the parent value in the version number (for example, the
We release cPanel & WHM through four publicly-available tiers. This production scheme allows us to rapidly develop and publish new versions of cPanel & WHM. Use the Release Tier menu in WHM's Update Preferences interface (WHM >> Home >> Server Configuration > Update Preferences) to select a cPanel & WHM tier that reflects the degree to which you value stability, new features, or update frequency.
|LTS||Long-Term Support. Some hosting providers do not wish to upgrade cPanel & WHM to newer Major versions. You can select a cPanel & WHM version for the year-long period in which cPanel, L.L.C. supports it.||Not applicable.|
|STABLE||We have given this version considerable public use and testing.||Published least frequently.|
|RELEASE||This version contains all intended features and functionality, and we have fully tested those features. New installations default to RELEASE.||Published more frequently than STABLE.|
|CURRENT||We have tested and verified this version. However, it may not contain all of the proposed functionality of a release. This tier represents the "Release Candidate" tier that other publication schedules use.||Published more frequently than RELEASE.|
We have given this version rudimentary testing. It contains features that we may modify further. This version usually lacks official public documentation.
|Published most frequently (up to several times per week).|
Some hosting providers choose to completely disable software updates in order to maintain control over their deployments of cPanel & WHM. The Long-Term Support (LTS) tier provides an alternative to disabling updates, and helps to ensure that cPanel & WHM servers receive important updates and fixes.
etc/cpanel/TIERS.json file contains a JSON file structure to indicate Long-Term Support.
For more information, read the following documentation:
End of Life
When a release of cPanel & WHM no longer exists in any release tier and reaches End of Life (EOL), we will no longer guarantee support for that release of software. Also, we will no longer release security updates and bug fixes for that release.
For information on EOL for third-party software that we ship with cPanel & WHM or operating systems that cPanel & WHM runs on, read our Third-Party Software End Of Life Policy documentation.
We release versions of cPanel & WHM simultaneously across several architectures. In addition, we may publish several versions across different tiers on the same day.
Whenever possible, we do not release new versions on international holidays and weekends (Thursday evening through Sunday afternoon).
In addition to everything in the previous production release, development releases of cPanel & WHM contain one or more changes from new projects for the next planned production release.
- We publish all development release changes to the EDGE tier.
- We only publish tested and verified development release changes to the CURRENT tier.
- We do not publish development release changes to the STABLE or RELEASE tiers.
We plan to publish at least four production releases each year with the following schedule:
- We publish the first production release around January.
- We publish the second production release around April.
- We publish the third production release around July.
- We publish the fourth production release around October.
We use the following process to develop and manage production releases:
- We complete development of the production releases.
- We test the functionality of the release's new features.
We publish the release to the development tiers, and to the EDGE, CURRENT, and RELEASE tiers.
Note title Note:
At this point, except for critical security issues, we no longer develop or publish changes to the previous releases.
- After the release enters the RELEASE tier, we assess any immediate maintenance needs.
- After we resolve the immediate maintenance needs, we publish the production release to the STABLE tier.