Lifecycle Milestones for VDI-in-a-Box

The VDI-in-a-Box product line follows the typical lifecycle policies and definitions described in more detail on the Lifecycle Phases and Lifecycle Milestones pages. Product specific information follows below.

For each major release of VDI-in-a-Box, customers will receive a minimum lifecycle of four years. The lifecycle consists of a mainstream maintenance phase for at least the first three years followed by an extended maintenance phase for the remainder of the lifecycle. The specific dates for each major release of the product will be posted within the Product Matrix Table or Legacy Product Matrix Table.

Customers that remain current in the Citrix Software Maintenance program receive 24x7x365 unlimited worldwide support along with product version upgrades.

During the mainstream maintenance phase, code level maintenance is provided by Hotfixes, Hotfix Rollup Packs, or minor version updates. When a major release (eg. 5.0) is maintained with minor version updates (eg. 5.1, 5.2, etc), a new maintenance baseline is established by the latest minor version update and it supersedes the previous maintenance baseline unless otherwise noted by Citrix. Citrix will typically provide technical support on the previous maintenance baseline but code level maintenance will only occur on the current maintenance baseline. Often to resolve specific issues, Citrix may require upgrading to the latest minor version update of a major release. When a new major release is introduced before the end of maintenance date for the previous major release, there will be two major releases that are each in their mainstream maintenance phases and each of them is independently maintained and supported as described above.

During the extended maintenance phase, code-level maintenance will be limited to security-related issues deemed critical by Citrix.

Note: These lifecycle guidelines are effective as of July 2012 and are applicable beginning with VDI-in-a-Box 5.  These guidelines will not be retroactively applied to earlier versions of the product.

Hypothetical Scenarios

The following table illustrates hypothetical scenarios for major product releases that have a three year mainstream maintenance phase followed by a one year extended maintenance phase.

1H
2012
2H
2012
1H
2013
2H
2013
1H
2014
2H
2014
1H
2015
2H
2015
1H
2016
2H
2016
1H
2017
2H
2017
1H
2018
5.0* 5.1*
5.2*
5.3*
5.4*
5.4*
5.4**
5.4**
         
        6.0*
6.1*
6.2*
6.3*
6.3*
6.3*
6.3**
6.3**
 
                7.0*
7.1*
7.2*
7.3*
7.4*

Legend

*  These versions are in the mainstream maintenance phase.
** These most recent minor version updates are in the extended maintenance phase.

Examples

  • Release of a new minor version establishes a new maintenance baseline for the code maintenance. Any changes to the code base, including Hotfixes, Hotfix Rollup Packs, Cumulative Updates, or new minor versions are based on the latest released minor version. For example, the maintenance baseline established with 5.1 shifts when 5.2 is released; the maintenance baseline for 5.2 shifts when 5.3 is released, and so on. As another example, if Citrix decides to resolve an issue that is discovered in 5.3 in 2H 2013, and that issue also affects 5.1 and 5.2, either a Hotfix will be provided for 5.3 or Citrix may chose to address it in 5.4 and ask the affected customers to upgrade or migrate to 5.4.
  • Each major version has its own mainstream maintenance phase so the same issue may be resolved in more than one place. If Citrix decides to resolve an issue that is encountered in the beginning of 2014, code level maintenance will be provided for 5.4 and 6.0, if the issue affects them both, because both of these releases are in their mainstream maintenance phase.

Take our short survey and enter to win your choice of an iPad Mini or a Nexus 7.

The survey will open in a new window so you can continue browsing the website.

Take the Survey No Thanks

Sweepstakes Rules