 I'm Matt Newsom. I'm the engineer manager at Red Hat responsible for the tool chain. So specifically GCC, G-Lib C, Binyr Tills and a number of ancillary tools for building RHEL and for building applications for RHEL. The developer tool set is a set of additional tools, the complement the tools you have in the base operating system and it gives you a newer compiler, the latest stable version from upstream and a number of complementary tools, performance analysis and debugging. When we put a version of GCC for example, the C and C++ compiler into base RHEL, we stand behind that for customers with a service level guarantee for 10 years and so we will fix security issues and major bugs that come up. What we find however is that over time the distance between upstream and the version in RHEL becomes greater and we had many requests from customers for a newer set of tools closer to the upstream. Developer tool set provides those newer tools and sits alongside the system tools so you have the option of using either the stable system version or getting the newer features from the newer version. Because the newer version sits alongside, when you build a binary with those developer tool set tools, you're actually just able to take the binary and put it on normal RHEL. There's no extra libraries or runtime that you need to put alongside it. From a developer's perspective, there are a number of real advantages to using developer tool set. So you have newer standard support for example, C++ 11, 14, 17. You have OpenMP and you have access to newer dwarf debug support. That's just in the tool chain. In the other tools, the performance analysis tools, we're similarly tracking with the upstream and so many new features are coming in. Some of the key users of developer tool set are in areas like the financial markets, in the animation studios and the national labs. They find there's a real benefit from having access to these newer tools. As a developer, one of the things I think is really useful in developer tool set GCC is the access to the newer standards. So C++ 11 and C++ 14 are already in there and fully supported and C++ 17 is already well on its way. The overlap between the upstream community process and the open standards process is actually very significant and Red Hat is a major contributor to both. It's a community and collaborative effort, but we are there in the standards meetings to help to find the next version of the language and we are taking that through to the prototype or often prototype version in GCC as well. As a great example of Red Hat's participation and contribution to the upstream process, we have one of the three release managers for GCC upstream worldwide. We have a number of the steering committee members on the Red Hat staff and there are a very large number of maintainers and significant contributors to the upstream project. When you build a binary with developer tool set, you're actually taking advantage of something we designed in called the hybrid linkage model. What that means is you don't need to carry extra libraries with your binary and for the most part you're using the runtime that is in base rel. So if you get a security vulnerability in a library in G-Lib C or LibStand C++ then a conventional fix for rel will actually solve that for you. In terms of support, developer tool set typically releases in the fall of each year. About six months later there will be a point update with bug fixes and minor updates and then it will remain in support for a further 18 months after that point. So it's a two-year life cycle with a new version every 12 months and typically we see customers move from one version to the next major version. Developer tool set includes a number of initiatives for containers so you can get Docker files within the product. Additionally from the Red Hat registry you can go and just grab a container image. We've done some light experimentation around that by taking a rel 7 base with developer tool set on top moving it over to Fedora and we found that you can build in there you can map in your source directories and so on. Now obviously we'd ask in terms of support that you reproduce any kind of bug on a base rel 7 system but from our experiments it seems to work great.