 All right, welcome to the product update. I'm going to talk a little bit about what we've been doing and the things that we're going to do. I didn't have time to add all these cool gifts, but it's definitely talking about the best release ever. So first, technical writing team is part of the product. And they're doing a lot of exciting things. And I wanted to highlight a few of the ones that I thought were really cool. First one being they've been adding crazy index pages to documentation. So many pages before were like a big table of contents that wasn't looking very nice. And now each page is getting its own input space. There's one for instance here for CI that I want to highlight that gives you a much better way to step into the documentation rather than, you know, seeing a table of contents has a million technical items. Now you can just quickly see, oh, this is how I get started. This is how I can do that. Makes total sense, but we haven't had that before. So it's good that we have it now. For if your screen is wider than very narrow, there's also not a table of contents to the site. So you no longer are first looking at the huge list, now you're immediately are facing the content. On the website, there's the comparison page. You can find it if you go to about to get that comparison. And we've added many things to this. There used to be this internal document that was send around with all these comparisons. And we took that, we took all the contents from that. It's all the comparison page and we keep adding to this. The goal is not to, you know, lead every person in the world to this page because, you know, we want to tell them about GitLab but not about the competing products. Do we still want to have a good idea of how we compete against other products and how, you know, what is the difference between Git Hub and GitLab and why is GitLab so much better? And there's obviously a hundred reasons and you will find a hundred reasons there. So let's talk about GitLab nine or two. Today is, I don't know what the date is, like 16 on the 22nd, we'll be releasing GitLab nine or two. We've been already working on it for a long time. It's already done, basic, most of it. And these are the things that we'll be shipping. These are the E things. We're still working very hard on disaster recovery. It's still on alpha, so we're still on the same. Okay, this is ready for everyone but we've been working very hard on it. And this release in particular has some nice changes that in the UI is more usable. And this may, might not sound like a big deal but believe me, people will be very excited about it. You can now have multiple assignees for issues. So rather than assigning issues to just one person, you can assign as many as you want. And this is one of those features that people really wanted and we've resisted for a very long time of implementing this because we have vision that if someone is responsible, they should be the one person talking about it. But this release will bring it. We also expanded the search capabilities with Elastic Search. So in GitLab Enterprise Edition, you have Elastic Search, which allows you to do much more powerful search. Let me open the chat in case, yes, there we go. And with this release, you can do much more things with Elastic Search. So you can say, I want an exact match or a partial match. These are really nice things and it's very, very useful if you want to search for GitLab for Enterprise Edition started. We also improved Approvals Further, which is one of the most used Enterprise Edition features. So it's very important that it works well and same with all that group sync. A number of things unfortunately slipped to 9.3 that I was very excited about, but they'll come up next. We're also doing a lot of cool things for C that I should definitely mention. I think the coolest thing is the scheduled pipeline. So it allows you to run a particular pipeline at a particular time. So you say, for instance, every Wednesday, I want to run the pipeline for this specific branch and then it'll run. We were actually planning on making this an Enterprise version, Enterprise feature, but the community contributed so then it goes into sync. And the next one, this is so cool. The Prometheus Sparkline in Merchant West Midget. So what this gives you is that when you make a change and a change is merged, it will show you what the state is of, in this case, memory. So let's say you make a change that is going to reduce memory usage. Gitla will actually tell you in the Merchant West that made that change how memory has changed when comparing the 30 minutes before and the 30 minutes after deploying this particular change. And I think that is the coolest thing because you get immediate feedback on whatever you've been doing. Not a really big deal is psychoanalytic. So what we're working on is translations in GitLab. And 902 will ship the first page. So we only translated one page, you have to start somewhere. And in this case, psychoanalytics, you will now be able to either put it in Spanish or German, so you just set a setting for what language you want GitLab to be in. And then psychoanalytics is the only page right now that will be translated. We're also adding real-time updates to issues. So right now you already have the title in an issue of dates in real-time. If someone changes it, you will see it just changing. And then next is the issue body. The reason that we want to do this is that we want to go to a place where everything happens in GitLab in real-time. So you're never looking at something outdated. And why do we want to go there? Because it allows you for real-time collaboration that in the future, everything will feel like Google Docs basically, where you see people editing. And it makes collaboration much faster, much more real-time. It avoids problems such as looking at something and then someone changed it and you missed it or you're editing something at the same time. These are really nice initiatives and this is a really good start of that. And then the last one is the ability to be in protected branches, which is something that was very hard to do. And we were hesitant to add a feature like this, but we edited it in a way that allows you to still do this safely, but allow you to do this if you have improvements on course. All right. All right, and then these two things are also exciting, they're also a nine and two. We released an official Helm chart and I actually announced it at the Build Conference at Microsoft last week. And the Helm chart allows anyone to quickly deploy something on Kubernetes without many more configurations. And this Helm chart allows you to deploy GitLab with runners and an external database on Kubernetes. So all you have to do is you have to do like two commands and you can deploy GitLab with all the scanning runners fully working on Kubernetes. And that is super cool because then not only do you get GitLab, which is already really good, but you also get all the extra abilities that we give you when you're using Kubernetes, like having auto deploy, deploying straight to your cluster. It's super powerful. And I think right now the most popular way to install GitLab is the omnibus package, just downloading it, using adcat. Second to that is probably the Docker install. I think in the future, this will probably be the most popular version and the future being like three, four or five maybe. But of course we want to do other things as well and Terraform is another way to deploy it. And in 901 we introduced the Terraform install and in 902 now actually support for runners as well, which is pretty crucial part of GitLab nowadays. So I'm very happy that that's there as well. All right, 903. So every month at the seventh, we start working on the next release. So we've been already working for nine days on 903. And these are the things that right now we're expecting to ship. First one being the first iteration of multi-project pipelines. Unfortunately, this is one of the things that we were not able to ship any part of in 902, but it's so exciting that I'm happy to talk about it more. Right now pipelines are restricted to a single project. That's very limiting. So allowing to create pipelines over multiple projects allows you to, if you have a project that has any kind of dependencies like GitLab has hundreds, you can have those somewhere in your pipeline so that when something changes in one of your dependencies you trigger pipelines of other projects that will at the end give you the new product. So even if a change doesn't happen in your actual project itself, one of the dependencies can trigger that pipeline. That's very cool. Enterprise Edition Premium Only. Another Enterprise Edition Premium Only is centralized audit logging. So it's very important for enterprises to know what is happening on their GitLab servers and that everything that happens is locked so that if something goes wrong you can look back exactly and see what went wrong. We have audit logging right now in GitLab but we're hoping to much improve this by having some form of centralized audit logging. So in 903, the first iteration of that ship. For Enterprise Edition Started we'll have the ability to relate issues to each other. So right now you can link between issues. If you just put a link there it will automatically say, oh, this is linked here and there. But it's not a formal relationship. And what we want to do is we want to introduce these formal relationships into GitLab. And the first step of that is with related issues. And in the future and I'll get back to that we'll expand this. We're also improving JIRA. So you can right now integrate and I think I made a mistake because I think this is a scene. You can integrate JIRA with GitLab and it's important because many people are using JIRA even though our issues are superior. We still want you to be able to have a great experience. So we've been improving this so that it's easier to set up. It's easy to configure and it's very powerful with the goal eventually that our JIRA integration is better than Bitbucket's JIRA integration. So that even if you're using JIRA there's no reason for you to start using Bitbucket because GitLab integrates better with it anyway. And of course we have GitLab.com. Tom says, JIRA and easy in one sentence. Well, it's easy to integrate with GitLab. GitLab.com, it runs Enterprise Edition but it's very confusing. So I'm not gonna say that anymore. This is the last time. Right now on GitLab.com you can buy subscriptions and the subscription will give you extra built minutes. And the goal is that in the future Enterprise Edition features are scoped or limited to specific subscriptions. And we're starting to do that in 9.3. So after 9.3 is released on GitLab.com you will need to have a certain subscription in order to get access to a particular level Enterprise Edition features. And the mapping is one-on-one. So if you're a bronze level subscriber you get Enterprise Edition starter features. If you're a silver, Enterprise Edition premium and sorry, of course. And then if you're a gold level subscriber Enterprise Edition premium, Enterprise Edition starter and in the future, Enterprise Edition ultimate. So you get a watch for all that world wrangling. So that's what we're working on 9.3. Let's see, do I have more for 9.3? No, very exciting. Of course, there's a million other things. There's also things that might have fallen over from 9.2 into 9.3. There's also things here that we might not ship for 9.3 but we'll do our best. So to finish off, some things that we are working on and things that I am especially excited about and I want to mention as well. For one, of course we're improving the ability to get a subscription for GitLab.com. The experience right now is just not very good. We wanted to introduce this as fast as we could because it allowed us to make sure that people have insight in how many minutes they use and buy extra if they need it rather than us saying, oh, you cannot use anything anymore. But we're gonna improve this whole experience so that you can sign up in the application. It's easier to see this kind of data and of course that the namespacing is all great. We're also working or we're starting to work on a Trello power up. We've been recently talking with the people from Trello and of course I think they have many millions of users and a simple power up that allows you because that's how Trello calls this integration that allows you to see your GitLab kind of data in Trello is very exciting. So I'm very happy that we're working on that. We're also going to be working on an official Slack application. So right now we integrate very well with Slack but it's not an official app. And Slack has like an app store where you can just click and you say, oh, I want this. So we've been talking with Slack. We are their number one mis-search. So when someone searches for something and they can't find it most of the times when they do that, that's GitLab and we want to solve that of course. It means that there's buildup demand for an application like this. So we're definitely going to do that and it's going to be very good. I already referenced this but we're working of course on internationalization. 903 world, we will translate the project and the repository page and this is a long ongoing thing, right? So we are shipping the first part and it's very simple. We don't have like easy ways to contribute. We have documentation but we don't have an application to easily contribute. We'll make all of that much easier in overcoming releases so that we have an organization that will help us with all the translation. What we want of course is that the whole community can help us contribute any kind of translation that they want. So overcoming releases we'll be working on not only implementing the translations but also making it easier for anyone to contribute them. I already mentioned the improvements to the JIRA integration and that we wanted to be the best one. We're still very hard, very committed to GitLab Geo that allows you to have a global replicated GitLab instance somewhere else on the planet so that if you have your main GitLab instances in the United States but in China you have a lot of developers as well that they can still quickly pull their projects. Disaster recovery, which is not the same thing and I hold off from calling it Geo disaster recovery because this is just disaster recovery that builds upon it. So we're working very hard on those two things and we know how important they are for enterprise solution premium customers. So very excited about that. It's super complex to build these things so we can do it faster than we are but we are very committed to it and it's been an ongoing thing. And lastly, I wanted to mention this. We are thinking about issue relationships and custom fields. So issue relationships, as I said before rather than saying just these two issues are related in the future in enterprise solution premium we want to give you the ability to say this feature is blocking this one so that it's easier to get an idea of what the state of something is so we can do some sort of reasoning from that point. And we're also thinking about ending custom fields in GitLab. It's something that we've also held off on implementing but we're now starting to think that this is something that enterprises want and might be interested in so it gives you the ability to say besides filling out the issue title in the description I can also add something like who is the best VP of product and then you can select your or no one else like something like that. We'll see how that implementation works. And that's it. My presentation was a little bit rushed but I hope you got a good idea. Let me know if there's any questions. You can also put them in chat or you can just speak up. I have a question for you related to the custom fields in issues. Yes. This is a very much requested feature for from the side of community. How are we going to the, well I'm using air quotes now defend the decision to do this in enterprise addition only. Well, as we do with everything right we have to evaluate how interesting, how important is it for these kinds of teams or actually how relevant is this for these kinds of things. And I think that custom fields is one of those things where if you have a small team the workaround is not really costing your organization anything. If you have a medium sized team the same goes. But when you have a larger organization you do not just have whatever workflow you want to achieve but you also have compliance needs, right? You need to have some way of forcing people to use a certain workflow to use certain things. I think that only exists in large organization or in organization that work as if they are large organization, right? So besides very large enterprises there will be very few small companies that need a feature like this and those that do you know they are basically working as one of these large organizations. So I'm not too concerned about this to be honest but it's everything we have to evaluate that and we're always willing to discuss that with the community as well. So Jim is asking how version.github.com is coming along that will be shipped in 9.2 Jim 9.2.0 So next moment let's see any other questions you can ask anything I saw on the direction page H8 package product is in 9.2 is it still like period? Yeah I was just checking with Marin I think the answer is no. Okay. I can comment just short on that Hayden we are working very hard on it we are shipping in 9.2 one smaller part of PGHA and we are working in 9.3 towards shipping well the complete solution for PGHA. Fantastic thank you. I have a quick question this may be more for marketing but as far as users seeing these updates these releases is the only way that they see that through the newsletter or does it pop up on any sort of other screen that they can be prompted to see the new features that are being released or is it just simply one email newsletter if they're subscribed? Yeah so this is a really good question and something I feel pretty passionate about so until recently the only way that we talked about these things is being new is through our release post so if you missed our release post and although it's likely that you did see it if you're somewhat interested in these things if you didn't see it then you were not very aware of things so there's a few things that work out the most important one is is that for larger new features right now in the application you'll start to see things like hey have you tried this feature or try out this feature so these little banners on top that teach you how to use it there are a few initiatives one of them is to do something like Select Us where they say on the top hey check out what's new and then you get like a little list or you get a link to release post but I also think that we can do a much better job in this so for the OKRs for the product we started to think about rather think about you know we should ship this many things we are focusing on that we want to increase adoption so that we start to think about how can we help people use the kind of power that we have in GitLab and how can we help them all more one thing that we're working on is the conversational development index that will basically tell you how you are using each part of GitLab's product suite and what kind of benefit you can get out of that including links to articles telling you this is how you should use that so there are several initiatives and I welcome any other because I do think that if we build things and no one uses it we might as well not build it so I feel very strongly about these kind of things is it as your question? yeah thank you and just we move so fast I know a lot of the clients you know they just can't keep up and I think that's a common issue so it's great that we're there's you know plans to fix that thank you Josh asked what isn't your passionate about I am indeed not passionate about Android as Sumaira said and I am also not passionate about peanut butter I never really liked it less chance for any questions I do like audio one cricket, two cricket the crickets thanks everybody see you in the team call