From the compelling Citrix XenApp and XenDesktop product announcements in 2016, the Long Term Service Release (LTSR) as part of XenApp and XenDesktop maintenance options has with you, our customers really resonance. We've received tremendous feedback on LTSR, including comments such as:
Citrix LTSR - Excellent news for us, "" We are for the next with LTSR Stick years " and "Citrix is showing some steps in the right direction with this new service opportunities.
This blog post provides a look behind the scenes in LTSR and shares some of the most important conversations I have had with the developers, engineers and product managers that our first 7.6 Long Term Service Release helped frame and the current financial framework to these new service opportunities.
First, I would like to go through a conversation I had with Juan Rivera, VP of Cloud & Server Technology), where we discussed how the shorter duration of the current release (CR) cycles product quality to improve.
Juan said that options model, we were on years of release cycles before the new service. Citrix Engineering would work on various aspects of the product over a longer period, routinely checked in hundreds of different code changes, while a variety of different combinations of tests run in parallel. The sheer number of code changes - even when evaluated through our extensive testing procedures - could result in unexpected behavior at a customer implementation
The new Current release cycle (remember, 7.8 and 7.9 are Current Releases) Citrix. Engineering is able to focus on a certain limited number of components and thoroughly test minor changes to the code, thereby improving the product quality of the components that are delivered as part of this rapid current release cycle. This is also why tougher to bring you see releases as often as Citrix operates more functions faster with the highest level of product quality top of mind. But if you feel like having longer cycles Update, Long Term Service Releases combine the advantages of several Latest releases in a single release for easier upgrade cycles.
with Juan My conversation was so enlightening that I thought it would be good with Ed Zimny to talk Sr. Director of Product Development cumulative regarding LTSR updates and related approval process ,
With LTSR there is an established base version for each component in the LTSR included. (Here is where you can go longer on the list 7.6 LTSR learning component). What I wanted was to understand from Ed how this affects the cumulative update release process. I have learned that it is important to understand that a cumulative update will be a single package that contains all the fixes -. A cumulative update targets only remind fixes
This means that Ed's team will be able to a single cumulative update test package that contains all of the updates. to test with a single cumulative update package, can Eds team narrow the unit test matrix down and more cycles to test a single collection of components together, spend focused the common user scenarios. This translates into a few key benefits: You will be able to install all the updates in a single package (which by the way also means less time worrying about a series of one-off corrections); and it also means that the components contained in this single package tested in a consistent manner along been, before they are released.
I extended my conversation with the lifecycle management (LCM) team and made a point to visit Yi Ye, Sr. Director of Product Development for Lifecycle Management (LCM).
Yi team is responsible for many things, one of which is the identification and preparation of post-ship product fixes. They have behind the new service opportunities in one of the major driving forces, since a basic version of components which will be his team allow corrections create faster.
might Da Yi knows that every LTSR problem that is reaching the LCM team based on a standard set of component versions that his team should be able to handle all fix inquiries at a more efficient pace have. Through all of the conversations that I had to have the luck with all the different engineering teams, it was clear that the new Long Term Service release will help to provide Citrix better service and help you to better your user community serve.
Last, but not least, I would Kireeti Valicherla, Senior Product Manager to mention that my manager was by all things related to LTSR.
he led the first LTSR release and product management connected team with a comprehensive LCM background, so I thought I would touch base with him about the latest updates regarding LTSR and the lessons we from the learned first publication. Kireeti spending time with the customer LTSR speak and to answer their questions, he mentioned how one of the most important improvements for the next LTSR to install both LTSR and the cumulative update will be.
Kireeti was able it will be to share a focus on simplified installation via a MetaInstaller that was recorded in Cumulative Update 1 for 7.6 LTSR. He also stressed that we have a new LTSR compatible version of Citrix have Receiver for Windows that can be downloaded here, and he would like the new LTSR Compliance try tool that will let you know if you are compatible and if you aren 't what you need to upgrade to be compliant. But I think the most important point is highlighted Kireeti the LSTR update to Windows 10 and 7.6 LTSR. Kireeti prepares your blog on this new announcement, so stay tuned for more information.
I hope you find my LTSR Behind the Scenes Tour to be informational and a big thank you to everyone who I mention that immerse myself in their field. If you have not read the Maintenance Options (LTSR) FAQ and Questions about LTSR, I suggest you check urgently. The FAQ answers your questions regarding LTSR release plans, understanding the current version (CR) compared to the Long Term Service Release (LTSR) differences, the new Windows 10 LTSR updates, and more. Hope this blog is to help you a little more insight into you to decide whether LTSR is right for you.
0 Komentar