Difference between revisions of "Releases"

From WHMCS Documentation

 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
This page defines and explains the different types of releases we make and the different distribution options we use and how you can apply and use each of them.
+
WHMCS makes several different types of releases and with different distribution options.
 +
 
 +
* You can [https://www.whmcs.com/members/clientarea.php download the latest full release from our members area]. We recommend reading our [[Release Notes]] and [[Changelogs]] prior to installation or upgrading.
 +
* For installation steps, see [[Installing WHMCS]].
 +
* For upgrade steps, see [[Upgrading]].
  
 
==Release Types==
 
==Release Types==
  
*'''Feature''' - A feature release introduces major new features and functionality.  It is denoted by a bump in the MINOR version number - x.X.x.  It will also contain bug fixes and other maintenance related updates as detailed below.
+
===Feature===
*'''Maintenance''' - A maintenance release addresses bugs and usability issues within the WHMCS product.  It is denoted by a bump in the MAINTENANCE version number - x.x.X.  It may also contain minor features, and/or additions/improvements to existing features.
 
*'''Targeted Security Release''' - A targeted security release contains changes to address one or more security concerns identified within the WHMCS product.  It is denoted by a bump in the MAINTENANCE version number - x.x.X.  Related maintenance issues either introduced by a previous TSR or providing considerable impact to users may at times be included but no regular or scheduled bug fixes will be provided as part of a TSR release.
 
 
 
==Distribution Types==
 
  
===Full Release===
+
A feature release introduces major new features and functionality. It is denoted by a bump in the MINOR version number: <tt>x.X.x</tt>. It will also contain bug fixes and other maintenance-related updates (see below).
  
A full release distribution contains all the files of a WHMCS product installation.  It can be used to perform a new install or update an existing installation (regardless of previous version).
+
===Maintenance===
  
It is denoted by the presence of _full within the zip folder filename.
+
A maintenance release may contain bug fixes and security updates as well as usability improvements for the WHMCS product. It is denoted by a bump in the <tt>MAINTENANCE</tt> version number: <tt>x.x.X</tt>.  It may also contain minor features or improvements to existing features.
  
The latest full release can always be downloaded from our members area at:
+
==Distribution Types==
https://www.whmcs.com/members/clientarea.php
 
  
*Release Notes can be found @ http://docs.whmcs.com/Release_Notes
+
===Full Release===
*Changelogs can be found @ http://docs.whmcs.com/Changelogs
 
 
 
'''Installation Steps'''
 
  
Please refer to the [[Installing WHMCS]] documentation page
+
A full release distribution contains all the files of a WHMCS product installation. It can perform a new installation or update an existing installation (regardless of previous version).
  
'''Upgrade Steps'''
+
A full release version contains <tt>_full</tt> within the zip folder filename and <tt>Distro Type: Full Version</tt> within the included <tt>README.txt</tt> file.
 
 
Please refer to the [[Upgrading]] documentation page
 
  
 
===Patch Sets===
 
===Patch Sets===
  
Patch Sets are often provided containing only the files that have changed between the immediately previous release and the Patch Set Version. We provide these to make updating both quicker and easier for those of our customers who stay current and up-to-date with the latest WHMCS releases. By including only the changed files, patch sets have less files to upload which makes the upgrade process quicker and simpler for you to perform.
+
Patch sets only contain the files that have changed between the immediately-previous version and the latest version (for example, a patch set for version 1.1.2 is '''only''' valid for a 1.1.1 installation). We provide these to make updating both quicker and easier for those of our customers who stay current and up-to-date with the latest WHMCS releases. Because they include only the changed files, patch sets have fewer files to upload, making the upgrade process quicker and simpler to perform.  
 
 
These will always include _patch within the zip folder filename to indicate they are a patch rather than full release version.
 
 
 
'''Installation Steps'''
 
 
 
Since Patch Sets contain only the files that have changed between the previous release and the Patch Set Version, patch sets are only valid for upgrades and cannot be used for new installations.
 
 
 
'''Upgrade Steps'''
 
  
Please refer to the [[Upgrading]] documentation page
+
* A patch set version contains <tt>_patch</tt> within the zip folder filename and <tt>Distro Type: Patch Set</tt> within the included <tt>README.txt</tt> file.
 +
* You cannot use patch sets for new installations. They are only valid for upgrades.

Latest revision as of 20:33, 2 May 2022

WHMCS makes several different types of releases and with different distribution options.

Release Types

Feature

A feature release introduces major new features and functionality. It is denoted by a bump in the MINOR version number: x.X.x. It will also contain bug fixes and other maintenance-related updates (see below).

Maintenance

A maintenance release may contain bug fixes and security updates as well as usability improvements for the WHMCS product. It is denoted by a bump in the MAINTENANCE version number: x.x.X. It may also contain minor features or improvements to existing features.

Distribution Types

Full Release

A full release distribution contains all the files of a WHMCS product installation. It can perform a new installation or update an existing installation (regardless of previous version).

A full release version contains _full within the zip folder filename and Distro Type: Full Version within the included README.txt file.

Patch Sets

Patch sets only contain the files that have changed between the immediately-previous version and the latest version (for example, a patch set for version 1.1.2 is only valid for a 1.1.1 installation). We provide these to make updating both quicker and easier for those of our customers who stay current and up-to-date with the latest WHMCS releases. Because they include only the changed files, patch sets have fewer files to upload, making the upgrade process quicker and simpler to perform.

  • A patch set version contains _patch within the zip folder filename and Distro Type: Patch Set within the included README.txt file.
  • You cannot use patch sets for new installations. They are only valid for upgrades.