 Hello and welcome everyone. Thanks for joining us today. We're excited to have you on. During today's webcast we will be going over our latest release 11.2 where we have lots of exciting new features. My name is Agnes and I work on the marketing programs team here at Good Lab. I'm joining you from San Jose California today. We'd love to hear where everyone is tuning in from so if you feel so inclined please use the chat function to tell us where you are in the world. Also joining us this morning is James Ramsey from our product team, Antonio Mimo from Field Sales and our presenter Simon Williams our account manager. We're going to give people just a couple more minutes to get locked on. While we're waiting I'm going to launch a poll you can take part in if you'd like. The graphic on the next slide may be useful as you think through your answer for the first poll question. Great thanks to everyone who participated in the poll. Before we get started I'm going to cover a couple of housekeeping items. First feel free to ask questions throughout the presentation. You can use the Q&A function at the bottom of your screen for that. We'll have dedicated time for questions at the end of the presentation and demo but you can go ahead and send in your questions as you think of them and we'll make sure we get to them at the end. If you're experiencing any technical difficulties you can use the chat function to get in touch with the moderator for help. Now I'm going to turn it over to Simon to talk about the results. Thank you Agnes and welcome everyone to our first release radar webcast for the EMEA region. I'm just going to go through the poll results quickly so thank you everyone for taking part. It looks like we've got a really good spread of people using different parts of GitLab. Quite a few of you are using the create part which is the traditional version control piece and we've got a couple of people on the webcast as well who aren't currently using GitLab so hopefully we'll give you some good overview today of what you can achieve with GitLab but if you do want any more information at all please feel free to reach out to us at the end of the webcast and we'll do our best to help you. Before James presents the demo to you I did just want to set the scene for what he will show you and talk a little bit more about what we've done with 11.2. So as you know or as you may not know if you're new to GitLab, GitLab enables concurrent DevOps by providing a single application for the entire DevOps lifecycle accelerating your development and delivery. I'm super excited to share with you some of the new features that will help you get started and iterate faster. Now rapid iteration is key to success in DevOps. It separates the winners from the losers and enterprises that rely on their software innovations get real competitive advantage. Here at GitLab we aim to practice what we preach. We constantly turn out new code to production and on last check we do between 40 and 100 code changes live every day. To do that we use our own product. It empowers our whole organization not just the developers to move quickly and gives us real business agility. Each iteration gives us an opportunity to advance and deliver real advantages to our customers. If we're off track we can learn about it quickly before any significant investment is made that might take us down the wrong path. So let's have a quick look at how 11.2 can help GitLab users do the same. Now again another bit of a plug for GitLab in addition to rapid iteration we practice consistency. 11.2 is our 86th consecutive monthly release. That's just over seven years. I'd had to do the maths to work it out. Just over seven years of releasing every month. We're very very proud of it throughout the whole organization. So let's look at three of the release highlights briefly before we move on to James's demo. Before I go on if you do want to look at the full detail of what's in 11.2 you can look at the release notes as well. I'll just pop those into the chat so that you can browse throughout your leisure as I'm discussing them. Before we launch into discussing them in a bit more detail let's have a quick polling question just to set the context for how we're going to talk about Web IDE. So Agnes if you could bring up the next poll for us. Perfect thank you very much. And for those of you who don't know GitLab's Web IDE I know there are a couple of you who don't use GitLab today. It's something that we introduced in June this year so it's still relatively new and actually very exciting as a feature to bring out. It really is aimed at helping to get you coding quicker with GitLab that you have a full IDE experience in your browser and it doesn't rely on having any local clients installed for example. Here we go the results are in. We have out of everyone it's about 20% of people that are using Web IDE today. Like I said those of you that are using it today that's great but those of you who aren't please do have a look at it. It's available in all of the tiers of GitLab so it's there available for you to turn on whichever version you are using today. So let's have a quick look at my screenshot. So the Web IDE really makes it faster and easier like I've said to contribute changes to your projects provides an advanced code editor with commit staging right within your browser. With 11.2 we've made it even easier to see the effect of your code changes and to debug even before you commit. You can now preview your JavaScript web app in the Web IDE. You can view your changes in real time right next to the code for client side evaluation. In addition with 11.2 you can delete and rename files and switch branches without ever needing to leave the Web IDE. This means you can see the impact of your changes easily and quickly without needing to change apps and context. Now in today's fast-growing development environment moving from an idea to setting up a new project from scratch can still be a tedious task. There's a lot of boilerplate code involved and additional admin overheads preventing your developers from getting started right away. With 11.2 we enable organizations to manage their own project templates. As a GitLab admin you can now define a group within your installation that serves as a source for custom templates. All the direct child projects of this group are available as templates when creating a new project. All the relevant repository and database information of a template get copied over to your new project including the project and wiki repository, the issues, project configuration and more. This lets you get started right away and allows the team to spend more time coding and less time managing the process. Until now importing complex project structures that have multiple substructures was a very tedious and time consuming task. With this release we introduce support for manifest files for project imports. Manifest XML file contains metadata for groups of repositories allowing you to import larger project structures with multiple repositories in one go. When creating a new project there is a new option to choose a manifest file as the source of your project import on the import project tab. In addition you can then select from the list of individual projects in a subsequent step if you don't want to import the complete project structure. That's what you can see on the screen here. This improvement allows you to import the Android OS code from the Android open source project as one exciting use case. You can also import other projects that use of manifest files which meet our format requirements. And as it always is every month there are a lot of other features that we've included as well in the release. So I'll just quickly talk through some of them here, some of the highlights. For me this is a great one. We're very excited to announce that the cloud native GitLab Helm chart is generally available. This chart features a more cloud native architecture with a container for each component of GitLab and no requirement for shared storage. These changes result in increased resilience, scalability and performance of GitLab on Kubernetes. GitLab runner is also deployed, making it easy to get started with GitLab CI and CD. The GitLab chart is the best way to deploy GitLab on Kubernetes. Please give it a try and let us know what you think. This has been a long time coming this project and we would love to get your feedback. In addition there are several more features which are aimed at efficiency, team work and collaboration. Now this is quite a cool one. I quite like this one as well. So within your profile settings in GitLab you can now add a status including an emoji and a custom message. This status will show up on your profile page as well as in your comments and author title bars. So across GitLab people will be able to see your status and the emoji exposing it to everyone that's working with you. The obvious example that springs to mind for me is whenever you're not available, for example you're on holiday and everyone would know that you're not going to be able to get back to them straight away. Next one is pretty cool actually. So instead of restricting search to the project or group that you're in, we can now give you a consistent experience with the ability to search instance wide from the top of every page. This is a really cool one for inner sourcing use cases that you might have where you want to search instance wide. Issue boards, they were originally designed to support workflow tracking with label based lists. In 11.0 earlier this year we introduced a sign-e list so that teams can easily see which members have got issues attached to them and reassign them quickly. Now with 11.2 we've got a third type of list coming, the milestone list. All issues assigned to the given milestone will appear in a milestone list. This allows teams to see the issues in different milestones all at once in one single board with multiple milestone lists. This also means that you can quickly move issues across the different milestones. Add in the next feature and it gets even cooler so you have summed weights. With this in 11.2 it means that you can see the total weight of the issues that are in the milestones and for the sign-e's as well, not just for milestones. You can make sure you're not over-scoping or under-scoping. The final one I'm going to talk about here is that when you're at mentioned in an epic you'll get a to-do for it. This just helps to streamline your personal workflow. You can also create a to-do manually from the sidebar when you're viewing an epic itself. Again similar to the capabilities that we already have within issues and merge requests. It just makes your workflow that much easier to manage. Enough of the bullets, a bit of overkill potentially there. Let's get on with the demo and I'm very happy to pass it over to James. Thank you Simon. I'm excited to give you a quick demo. I'll just share my screen. Thank you. Here we are in a project and I'm going to show you a bit about the Web IDE. If you haven't used the Web IDE before, the easiest way to jump in and give it a try is by clicking the Web IDE button. As Simon said, this is available in every edition of GitLab. This project to give you a bit of background is a little toy project I've been working on trying to learn a bit of Vue.js. It's a simple to-do app. We can see there's a bunch of files here that I've been working on. There were a few improvements that I need to make and I've started on a merge request to make them. If I open this merge request and we can also open the Web IDE right from here. I haven't added a done button yet. Let's take a look. This is the Web IDE. It's opened one of the files that I changed in my merge request. This probably doesn't mean much. We can take a look at the new Live Preview. Clicking the Live Preview button launches a code sandbox side by side in your IDE and we can preview the app live. This is a to-do app, so I can add it to do. Try out GitLab. Switch to GitLab. We can mark some done. I suppose I've learnt Vue. I've got some single component files. I'm pretty much in love with it. I'm marking all these items as done, but the button says X. This feels like a delete action. This is one of the improvements I want to make. If we take a look at the source code, we can make this say something a little bit more useful. I think it's in this file. Yes, it is. Here we can see the X button. I'll verify that that's the right button. There we go. I've made a change and you can see it applied live. This is, I guess, the dream development scenario. You're making changes and seeing your code live. I think we can maybe do better than a done button. What we'll do is add a new component, which has an SVG. We'll see what it looks like to have an icon in the button. In the file tree, we can create a new file in the components folder. We'll call this done button. Just like using your local development environment, we can create files. I need a new template. I'm just going to copy and paste in an SVG, which is from our component library at GitLab, which is public if you want to take a look. This is an SVG for a check mark icon. Still not visible because we haven't yet added this to our view list item. To do this, I need to import from components. I think actually the components is not necessary. Now we need to include the component. I've misnamed that. That's why I've got a compiler error. Cannot find the module. Components. What have I done here? Done button, done button. Let's see if we can use this component. Done button template. Sorry, I've probably made a very trivial typo. Done button, components, done. Let's commit this and reload it. To commit the change, we click the commit button. These are my changes. Done button. Stage and commit those. Let's just reload this. Try the live preview again. Okay. This is better. We still can't see the icon, though. This is what I wanted to show you a live preview. The great thing about live preview is that if you make a mistake, you can fix it before you ask someone to review it and it's broken. What I've done here is I've forgotten to add a height argument to my icon. It wasn't rendering. 12 is a bit small. Let's see what 24 pixels look like. That's a bit weird. Maybe 14. Yes, I think that's a bit better. I'll commit that now that I'm happy with that. Okay. Fix missing button. We'll stage and commit that. I can commit it by double clicking it. This is how you can use the Web IDE to add improvements to your applications, even create a brand new web app from scratch, fix bugs, or address code review feedback. That's my favorite use case for the Web IDE. When someone leaves feedback on one of my merge requests, I can quickly open it straight in the Web IDE and fix the typo or fix the bugs that I've created inadvertently. The next feature I'd like to share with you is about project import and export, which I will go to not project import and export. Project templates, which I'll explain why I had that documentation page open in a second. In 11.2, we've added project template support. I'll show you the group where we've got some project templates. The project templates feature allows you to create custom project templates and add them to a repository. Here, we've created a simple to-do app project template, a spring template, and a minimal Ruby template. What this allows us to do is when we create a new project and we create it from a template, we now see the GitLab built-in templates, but also the custom templates. The really exciting thing about this is you can add templates that are specific to your organizations and teams so that they can get started. Really quickly. An example might be microservices. If you're using microservices, you could have a template and every time just get it right very quickly in a single click. There are quite a lot of things that get created with a project from a project template, the Wiki contents, the project contents, any uploads, webhooks, issues, the things to draw attention to that aren't copied across CI variables, container registry images, and build artifacts. But if we create a new one from the spring template, we use this template. I'll create a new one. This is my called SpringTest. Create new app. I'll make it public. I've already created a test. All right. Oh, dear. I think I cleared my settings when I had the typo. So let's use this template, create a new one. Spring app. Create template. Here we go. So this is importing the project and it's copying over all that data I described before into our new repository. And here we go. I've got all my files that were in the template. It's going to have copied across all the settings. So you'll see that any permissions around project capabilities. So LFS was disabled in that template. The pipelines were enabled. Any issue settings or merge request settings, these are all copied across. So if you've got a specific way of doing things in your organization, you can use project templates to quickly replicate those when you're creating new projects. So it's a really exciting feature for organizations using GitLab. The next really exciting feature I'd like to share with you is around importing Android manifest files. So the Android project is actually open source project consists of multiple repositories. So I can jump back here. So all of these are different repositories that need to be created in a specific structure to work together. And it's a bit of a pain to create this many projects. And so what the Android project has is a manifest file. And you can now use a manifest file in GitLab to quickly import a subset or all of these repositories into your GitLab instance. So I'll show you how to do that by creating a new project. And I'm going to import a project. And I cannot see the option. No, I am sorry. I can't demo this to you right now because the button is not available. So I may have done something wrong here. All the staging environment might be running a different version than I'm expecting. I apologize for that. But basically, you would click on there's a new manifest file button that allows you to upload a manifest file. And it will give you a list of every single repository here. So each one of these is a repository. And you can then select individually which ones you want to import or click an import all button. So finally, I'd like to show you the milestone board. So this is this is GitLab.com here. And this these are the issue milestones for the GitLab.org group. So you'll see these are milestones for some previous releases. We also have milestones for all our upcoming releases. Sorry, scroll past them too quickly. Down here we've got 11.5, which is coming up soon in October November. And we use these in the issue boards. And so this is the new milestone list. So this is the milestone board for my team. You can see these are the direction items that we're working on for 11.4. We can see how many issues and what weight they are. And looking at the distance, we can add issue columns for upcoming releases, upcoming milestones, 11.5, next three to four releases. We can add a new list. So I'll add another milestone because 11.6 is coming up very soon. And I've already added a milestone, already added an issue to that. I probably need to add some more great features to 11.6. But yeah, this is how you can use and how we use the new milestones lists in the issue boards. So Simon, I'll hand back to you to wrap things up and take questions. Thank you, James. That's I mean, I personally just love the web idea. I think it's such an exciting capability to have within the product. I'd love to see what's going to evolve from where we are today. But it's not time to talk too much about us. And what we're doing is time for you to ask us questions. So I'm throwing it open to the floor. Now for Q&A, anyone that has questions, please just let us know. There should be functionality for you to just chat it to us. I'm going to just add, I've already done it, the release blog post about 11.2 if you want to see more details. But in terms of questions, I'm just going to bring it up. Agnes, have you had any come through yet? Yeah, we don't have any come through yet, but maybe we can start with some questions that, you know, we have seen come up a lot. So one, when are we going to do the server side evaluation? Seems like James did a sneak peek right there in the demo earlier. So James, maybe you want to pick this one? Sure. We're actively working on server side evaluation at the moment. And we're very excited about it. The first iteration is coming in 11.4. And it is a web terminal powered by server side evaluation. So the really exciting thing about that will be that side by side with your code, you'll be able to run unit tests and pull up a REPL interface to your preferred language and will support any language that you can run in GitLab CI. So server side evaluation will be powered by GitLab CI. And the actual live preview of web applications will come in, I think 11.5 or 11.6. But we're working on that at the moment and that will be an ultimate feature. Thank you, James. All right, maybe another one that a lot of people are curious, what is Helm? So maybe Simon or James, you want to take that? James would probably give a better answer than me, but Helm is a way to get started with installing with Kubernetes. And the important thing about it for us is that we've now got all of the GitLab application can be installed using a Helm chart. It was previously in beta. I think it was in beta for quite a while, maybe six months or more, but it's now generally available. So you can take that Helm chart that's available, install all of your GitLab application so that it's cloud native and get all of the benefits from using a cloud native architecture in terms of scalability, resilience and performance, right for all of your GitLab users. Awesome. Thanks, Simon. I guess if there are no questions, we will close up with one that, you know, again, comes up a lot. So what format is required for the manifest files? The manifest file format is an XML file format. It's documented in the GitLab documentation. I can paste a link quickly in the chat. And so it's the same format that Google uses for the Android project. And there's more detailed documentation available on the Google page, Google website as well. So here's the link to take a look at the manifest file. All right. Thank you, James. And here is us actually commented and says it still has Postgres that may not scale like other cloud native DBs. So I think it's a comment. Thank you, Iza. And Marco sent over a link to all the panelists on Helm. So thank you, Marco. All right. If we don't have any other questions, maybe let's kind of move on and close up with like a little bit of tease on what's coming up with 11.3. Go ahead, Simon. Yeah. So 11.3 is right around the corner. It's 10 days away because we release on the 22nd of every month. It's always the case that something shiny and new will be available very shortly with GitLab. 11.3 is no exception. So I will just post into the chat. There we go. The link to all of the releases and you can see exactly what's in 11.3 there. But 11.3, some of the highlights that I've picked out protected environments, I think is really an interesting one and is really good for the GitLab admin teams to look at in terms of just controlling who gets to deploy changes, for example, to production or to staging if you want to protect your environments that GitLab's deploying to. There's a bunch of improvements from our planning team, including some improvements to Epics and Roadmaps. For SAS, we're including Groovy to the languages that we support. And there are a host of other features that I won't go into now, but please do check out the link in the chat so that you can see more details on them. As always, it includes links to the specific issues themselves so you can comment and give your feedback directly in those issues straight to the product teams. And on that note, that's it. That's my time. I'm going to hand over back to Agnes just to say for me, thank you very much for your time today, everyone. Thanks, Simon. All right, so just a few last housekeeping items. We'd love to hear your thoughts on today's webinar. So please fill out our webinar survey, which I'll drop in the chat today. Here you go. And then finally, if you have any other questions, please don't hesitate to reach us via our sales contact page about.gitlamp.com slash sales. That's all for today. Thank you so much for joining us.