Citrix xenapp/xendesktop Product Release policy tuning

At the 2016 Citrix Summit Conference, Citrix provided a more flexible and pragmatic release rule for its core product Xenapp/xendesktop product update and release cycle, which will be on the premise version of xenapp/ XenDesktop products are divided into the following two new release modes:

1. Long TermService Release, abbreviated as LTSR version,

2. Current release, referred to as CR version.

650) this.width=650; "title=" Ltsr1.png "alt=" Wkiol1age6tzsplxaacj5typru4230.png "src=" http://s3.51cto.com/wyfs02/ M00/79/ff/wkiol1age6tzsplxaacj5typru4230.png "/>

The main features of the LTSR version are:

1. A more stable version is selected every 1-2 years to be calibrated to the LTSR version, which will be available for 5 years from the date of release, and 5 years of extended technical support services, that is, a maximum of 10 years of service.

2. LTSR's original intention is to provide a stable and long-time technical support version to the customer. Applies to users who have no expectations for new features and want to use the most stable version.

3. The LTSR version will select and solidify the version of the core components, including XD/PVS/SF, and the supported operating systems, and launch the cumulative update as planned to ensure product stability and the supported functionality.

4. The first LTSR version was built on the basis of Xenapp/xendesktop 7.6 FP3,

The 5.LTSR release will not provide new features in any new releases after this release, unless you select the next version of the LTSR version.

6. Unlike the initial release date of a large version of the EOL time of a previously delivered version, the LTSR version is calculated starting with this release time. So does not appear in the XD5.0 era, the deployment of the XD 5.6 version must use the XD5.0 eol time issue.

In contrast to the official product lifecycle time, we can see that if the 7.x version is selected, then the EOL time will be in 18, and the EOL time will be in the year 2021, while the LTSR version is selected.

650) this.width=650; "title=" Ltsr2.png "alt=" Wkiol1agfbmrvt4maabvbv43mz8047.png "src=" http://s5.51cto.com/wyfs02/ M02/79/ff/wkiol1agfbmrvt4maabvbv43mz8047.png "/>

The main features of the CR version are:

1. The CR version is designed to meet the current customer requirements for new products, new technology updates faster. Recalling the pace of update xenapp/xendesktop 7.6 we can see:

September 2014 7.6RTM Xenappenhancement

March 2015 7.6 FP1 New receiver,session Recording

June 2015 7.6 FP2 Framehawk, Linux VDA

September 2015 7.6 FP3 Windows 10,

December 2015 7.7 MCS on Azure, Zone

Subsequent:

2016 Q1 7.8 AppDisk

2016 Q2 7.9 Unknown

As we can see, a version is updated almost on a quarterly basis, with new features being fixed and bug fixes to the previous version, improving the overall delivery quality of the product as a whole.

Other precautions:

1. For LTSR and CR versions, a valid SA is required during the update process, which is consistent with past management requirements.

2. The same farm can have both LTSR version and CR version, but need different site to manage separately.

3. Functional components such as pvd,receiver are not in the LTSR version management category.

4. All XenApp, xendesktop versions are available in either LTSR or CR versions.

This article is from the "Citrix in the Cloud" blog, be sure to keep this source http://kaiqian.blog.51cto.com/236001/1737129

Citrix xenapp/xendesktop Product Release policy tuning