Video: Liberty single-stream fix pack delivery

The following transcript is for the 16.0.0.2+: Liberty single-stream fix pack delivery video, which describes how Liberty content is continuously delivered, the new single service stream for fix packs, and the new fix pack numbering scheme. Audio describes narration and captions. Onscreen Action describes the content that is shown in the video.

Video 16.0.0.2+: Liberty continuous, single-stream fix pack delivery

Table 1. Continuous, single-stream delivery of Liberty fix packs
Scene	Audio	Onscreen Action
1	With the release of WebSphere Application Server Version 9, we're sticking with a single service stream for Liberty fix packs, which will be continuously delivered. What exactly does that mean? Let's break it down.	Show words, 16.0.0.2 and beyond: Liberty single-stream fix pack delivery
2	Liberty has always followed a continuous delivery model, so that you can get new functionality faster than traditional models. Traditionally, new functionality is released in large chunks as a new product version, with smaller updates and fixes being delivered as fix packs in between versions. This means if you want to try out a new technology, you might have to wait a while until the next version. With the Liberty model, functionality is continuously delivered, so there's no need to wait for the next big version - just until our next regular update.	Show words Liberty continuous delivery: A refresher Show a graphic that has lots of pieces applying to a new version and only single pieces applying to fix packs to represent traditional models. Show a graphic that spreads the same number of pieces evenly across fix packs to represent the Liberty model.
3	New versions no longer deliver a large amount of new function - it's all about the fix packs. With single-stream fix pack delivery, all Liberty product versions get the same fix packs with the latest and greatest updates. You get the same content on the same schedule, no matter which product version you purchased. Fix pack 16.0.0.2 and beyond apply to both WebSphere Application Server Version 8.5 and Version 9.	Show the words Single fix-pack delivery stream Show a line of fix packs with an arrow that is labeled WebSphere Application Server Version 8.5 Show a block that is labeled "16.0.0.2" to represent that fix pack, and show an arrow that is labeled WebSphere Application Server Version 9.0 that starts at the fix pack and continues.
4	Fix pack 16.0.0.2 - where does this number come from? With the single-stream continuous delivery model, version boundaries are no longer as significant. So, we're introducing a new fix pack numbering scheme to highlight what is important - how your Liberty installation is. Instead of the traditional version, release, modification, fix pack numbering scheme, such as 8.5.5.9, Liberty fix packs now begin with the year the fix pack is released. For example, 16.0.0.2 refers to the second fix pack of 2016, the first being 8.5.5.9, which was still on the old numbering scheme. The first fix pack of 2017 will be 17.0.0.1. So, in 2018 you can look at your 17.0.0.1 installation and know that it's about a year old, and it might be time to update.	Show the words Year-based numbering scheme Show the word 16.0.0.2 and question marks. Show the word 8.5.5.9 with the words version, release, modification, fix pack labeling each number. Show the word 16.0.0.2 with the words year, release, modification, fix pack labeling each number.
5	When it is time to update, the Liberty zero-migration architecture means that you don't have to worry about reworking your server configuration or applications. The server configuration is fully backward (and forward!) compatible, meaning that configuration for a newer release works with older releases, and older configuration works with the latest release. This means that if all configured features are installed, you can use a single set of configuration files for many different Liberty versions. Except for feature configuration, any items that do not apply to a particular server are just ignored. Liberty packages API support for your application in pluggable features, which you can enable and disable to customize the technologies available in your server. If an API changes, such as Servlet 3.0 to Servlet 3.1, you can continue to use the `servlet-3.0` feature and don't have to rework your applications to account for any behavior changes unless you choose to enable the later specification level.	Show the words Liberty zero-migration architecture Show a diagram that shows a single set of server configuration that applies to a Liberty 8.5.5.2 server and a Liberty 16.0.0.2 server.
6	To learn more and to download the latest Liberty fix pack, visit WASdev.net.	Show the words, For more information and to download: WASdev.net Note: The WASdev.net site mentioned in the video is no longer available. For more information about downloading the latest Liberty fix pack, see Installing Liberty.