 All right, welcome everybody to the product update of today And I try to keep it short so that there's lots of time for questions So today I'll I can't change my slides. Oh, there we go today. I'll talk about There's some like two highlights of what is what is new What is very cool and some things that I've learned recently which might be interesting to you or not Latest we I hired a new product manager. He is starting May 1st. So that's great That's all for the product team new so far cool stuff in 10.6 we released CI CD for github and It's still rough in terms of user experience, but it works incredibly well Meaning that once you set it up. So you have a repulse story on github You set it up. It works like magic your you can do everything you want in github You can create a pull request as it's called there which is totally one way to call it and You just see the CI status appearing straight from github CI you can click on it You go straight to the output of the CI Very very cool. And the nice thing is I already heard From customers directly that this is something of potential customers that this is something they want because many people are stuck on A tool that they're probably chose for instance github or Bitbucket and they still want to be able to use github CI So this is a super big deal and Worth while sharing with all of you Other thing which I should mention for 10.6 that we released is a single group board in Libre Now you might wonder why do you call this audio? We have as an organization we built the product we built github, but at the same time we have A role for stewards to the open source project, right? The open source project is not owned by us It's owned by everybody it's open source and we are just being a steward of that and being a steward of an open source project Means that we have to make sure that we continue to invest in it and it continues to stay Good and we need to think about that all the time and our product managers all know this and So I was very happy that in 10.6 we did specifically for Libre What we did is we created a feature that is not as expensive and as deep as the group level issue board We have in github premium, but it still gives some of that Power to everyone else that's that can't afford github premium. So very excited about that very important Let's go over to 10.7 I only have one highlight for 10.7 because you'll hear in all these functional group of dates from all the specifics This is very big deal. So in 10.7 we're releasing single sign-on for github.com So in other words it allows you that if you're a large organization and you have something like LDAP set up To actually use github.com even with your own single sign-on methods So this is huge as rap appropriately says in the chat. This means that Basically any organization can just adopt github.com and they don't have to run on premise anymore and Running it on premise is fine. It's very easy and it's very doable But if you don't have to why not just use github.com and this was one of the few things that we're standing in the way We spend a lot of time over the past. I think 18 months if not more Making sure that if you're using on premise or com there's no real difference in terms of features And this was one of the last things standing in this way. So this is still an early Version of this right so it but it works and it will allow anyone to use this and we'll continue to invest in it and make sure that The cool features you get with this that you get if you are on premise you all have on github.com so Super big deal and I wanted to highlight that because I think many of you would agree that you know today 99 95 percent of Our customers and of large enterprises run everything on premise But in the future in a few years it's going to be 50 50 and then it's going to be 70 30 So making sure that we are ready for that is incredibly important Everyone works very hard to get levels common. This is stuff that the product team is worried about that specifically Jeremy has been worrying a lot about So I wanted to highlight that Now some things that I've learned recently last week I was in London at the cloud expo, which is this big conference. I spoke to a lot of customers. I spoke to a lot of influencers, whatever you want to call them and a lot of colleagues, which was very great And there's a few things I've learned and I want to summarize in like two points Which might or might not be interesting to you first off Issues are popular at github. Of course we use issues and issues works a lot And so we don't know any better, but there's about a count of the other day I think there's about 1.3 billion different project management solutions and nonetheless GitLab's issues are incredibly popular GitLab issue boards are incredibly popular had so many people come up and tell me that They're switching away from the old project management solutions to get that issue So anything we could do to improve this and these are of course big things like epics But also small quality of life improvements are very important and very loved by the community So this was nice to hear and I thought very exciting I was two days ago I was at the University of Porto and they were telling me that rather than using Jira or they use Bifthal tracker before Now they started to use for all the internal projects GitLab issues And they said it was a huge success and everyone loved it Some people use GitLab issues together with the repository somewhere Some people used all of GitLab very cool to hear The thing was not by on purpose, but it did sound very nice Kubernetes which is the way I was told by one of the creators of Kubernetes to pronounce it So if you hear someone else pronounce it differently, I got it from the source Kubernetes is huge. So you know that this is one of the fastest-growing open source projects of all time And you know we are betting very heavily on it But with these kind of new technologies what you usually think is that well There's a lot of people excited about it and a lot of people talking about it But maybe not a lot of people actually using it and when I say people I mean large enterprises Kubernetes is not like that Everyone I spoke to is doing something with it. They are either in Further stages that you would imagine of moving towards Kubernetes. They're exploring it heavily or they're investing heavily I was expecting that most people would have something to say about and I was still surprised with how big it is And what the immense interest and power behind this movement is and this is a big deal because it Validates our strategic choice to pursue this right that we invest a lot of time We want to make it very easy to integrate Kubernetes deploy directly to it, etc And it seems to be actually as big or even bigger than we thought it was and many people think it is And Then the last one and this one is important whenever you go to a conference And together with GitLab, you know, we're staying there to booth You get two types of people roughly right you can separate to be people that know GitLab and people that come to the booth They self-select they love GitLab. So it feels very good. But then There's a large group of people that barely have any idea what GitLab is many people think it's part of GitHub Which is of course something we have to teach them about that it isn't But there's also just a lot of people that are not sure what it is that GitLab offers exactly right They might say well, I am aware of GitLab. I've heard of it But I don't know what they exactly offer if you're not someone that frequents hacker news And you're not someone that is you know, particularly involved in daffos in the organization that you're working in You might not know that GitLab has a CI component or even more than that, right? There's still a lot to win in terms of mind-share in terms of teaching people what we offer and even if you think about in terms of What people are using today, you know, we live in a world where CI is a normal thing and you know Doing everything containers is the most normal. It's old by now, right? Like I'm with my head at serverless And I spoke to many people that said well, we want the CI but we're not that advanced yet And these are all potential users all potential customers and we still have a lot to win there So I thought it was good to always put it in your head That's you know, we might be thinking about what's happening in the future But there's also a large large group of people that in organizations that still have to get to know GitLab at all I still have to learn how CI works and why you would you know, put your CI definition and follow your reports story So and as a last reminder, GitLab 11 June 22nd, there's an issue should be easy to find Super big deal, but until then we're still releasing GitLab 10.7 and 10.8. So with that any questions I'll check the chat first, but you can also speak up see Victor asks anyone else thinking about kill bill when watching this FGU it's because I like these colors Larry asks as a steward what role do we play? How do projects features get selected? How does this work? Let me stop sharing so you can look at me and One role we play a very big role We have to decide whether a feature lands in any particular tier and we have Liberally documented this on our stewardship page. So I would urge you to check that out It's about that kid little comm slash stewardship Now we describe the process that we used and the decision that we make we get it wrong sometimes But the nice thing is that if you get it wrong, you can always restore it. So We often bring things from a higher tier to a lower tier or even to a Libra. Let's see Else ask why are issues so popular? It's a combination of a few things We want issues to be flexible and easy to use that is very hard to do if you also want to make a powerful issue tracker So we try to find the combination between being opinionated So offering tools that we think work best for you while not putting the user in a situation where they're forced to go through Particular workflows or where you have the possibility to configure them in such a way that you're forced into a particular workflow The balance is very hard to strike but so far we've been managing to do that. So You you could describe good lab issues today as more advanced than what get up for instance offers But much more flexible and open and free than what Jira offers And I think that is that is the reason the fact that it's in the same place where everyone else's all their work helps a lot of course Mark Bell gives a nice anecdote of a Customer moving to Kubernetes in a big way. So this is very very nice to hear Brandon says is there an issue open for making a get up integration for CI CD work With get up enterprise not get up to go. I don't know if there's an issue open But if we should we should open it what we have in any way is that you can Run it with any external repository. You just don't have the full integration setup So I think for now, it's just to get up.com. There should be an issue for this. Anyway, and I think same for pit-pocket the numbers Rep says what big item are we expecting and Levin points here to go to a new release number? Discusses pain in many large organizations require all sorts of additional tests between major release of product Well, we're still working on what we want to decide exactly in terms of big features for us The major reason to do a major release is so that we can get applications out of the way We want the For instance to deprecate an old API pass a few other things and a major release is the best occasion for this I hope that in terms of complete DevOps like the first wave is is mostly done Which I think we will reach is is is June 22nd end of Q2 because then we will You also to add we had discussed when to release 11.0 So it was not in the peak summer vacation time or close to our summit. There was the other Yeah, yeah, this this is to do with the timing. Thanks. She's we don't want to release in a time When no one is actually paying attention to the news or we are all at the summit which is tricky, of course And Max says plus one my previous team switched to Trello boards because of the heavy configuration need to enjoy that So yeah, so this is a clear competitor to us, right? We have good live issue boards There's Trello, of course now Atlassian So we want to make issue boards better than Trello in every way And and doing that will allow us to get those people as well All right, still have 17 minutes for questions Don't ask did I buy a new TV idea this is in the background so I'm in the middle of a move so the whole house is full of boxes and The new TV is ready to be moved moving on Friday and Thursday Hey, oh, I have a question. I have a customer that just bought a Dot-com silver subscription and I want to send them information on the upcoming SSO I'm not finding it on the direction page. Is there an issue or what do I find them information? Well, I apologize. It's not on the direction page. Jeremy will make sure that ends up there within Within the time of the team call and he will also send you a link So you you will get the information John Woods, are there any thoughts on building a Jira GitLab important for issues? Yes, there are thoughts There's an issue and there's a plan and I hope to do it earlier rather than later Victor will leave a link there with the exact plans laid out There's some trickiness to building these kind of importers if we wait a little while with it We might have more features that allows to make Importing easier if we do it immediately then if we add additional features we have to update the importer So it's a bit of a balance, but we want to do it as soon as possible One thing that we did actually in 10.5 is that or is 10.6 This ability to link an external issue tracker next to get lab issues So if you are in a project, you can link to Jira and you can quick have a direct link to Jira But because you also have good lab issues there the transition becomes significantly easier so it's one way that we try to reduce the need for and They go all at once important and rather make more of the transition I think someone said at the conference I think those Ralph that said we should think about transitioning not about migrating migrating sounds painful and Victor of course supplies a million links in the chat and Drew says major release is getting more frequent and as a result. I think less painful Anticipate that 11.0 will be even more painless than 10.0 probably and I think so too them The most releases of kidnap the the migrations have not been very painful They used to be very painful in like six points something nowadays. They are not Say beyond as what was the reason to go to 11.0? There's a few reasons if you have major releases too far apart You end up with a lot of stuff that you can't deprecate, right? You need to have a moment to deprecate these kind of releases So to have a regularity to it is a very good reason to have a major release It gives us the opportunity to deprecate things And because I wanted to do it in a near to short term somewhere in in this year and preferably Before we would do 10.10, which doesn't look very good. And this came out. This is the best time and Josh says because kidnap now goes up to 11, which is a very good reference All right, three more seconds for any questions two one A new guy question from dan. Is there a single place online? At least all the past releases and their major themes Yes, about the kidnap.com slash releases Some will leave a link. Thanks it All right, and I have to start three three condoms from three again three two One all right. Thanks everybody. See you at the team call and otherwise in five weeks in the next functional group of it