 can you guys see my screen? Yes, I see it thumbs up. Good. Oh, and I think it's time as well. It's four here in Portugal and it's time for the product update of March 7th. So I'm going to keep it really short this time because I wanted to give all the space to the most important thing in the world, which is the Gitlib.9. And March 7th is a special date because the day is the three. So that means that today in the background you'll hear my dog coughing. It's very sad, yes, it's a cough. On the 7th we have the feature three. So basically on the 7th everything has to be done that we want to have done on that release. And March 7th in particular especially because it's done for 9.0. So that means that tomorrow nothing will be merged into the master branch of Gitlib anymore and we'll start making the first release candidate. So we have a very good idea what is going to ship, although not everything that I will say today here will be promised to actually ship because we still have it till the end of the day. So on that note let's talk about 9.0. March 22nd we'll release 9.0, the latest Gitlib release and the first major release in almost 16, 17 months. It's a very long time and hopefully a shorter time next time. But it's a big deal. So what are we going to ship in Gitlib.9? The first and most important thing and I think maybe the most important thing that we've shipped in a very long time since merging CI is subgroups. So subgroups allow you to have multiple nested groups. And that means that traditionally we have now GitLab org is the group and then you have for instance the project GitLab C that you see there. But what this allows you to do is have multiple groups inside of each other like folders or your computer. So you can have GitLab and then in that you can have a group called community edition. In that you can have a project called backend for instance or you can imagine that you have for instance a group inside of the GitLab group called website inside of that one one and blog and then a specific project for the articles. And this is a really big deal because if you have very big projects they don't typically exist from a single project. They don't exist out of a single repository. Even GitLab itself the core of GitLab, GitLab community edition is a single repository but many of the components of GitLab are in separate repositories and it makes much more sense if you're able to nest them like this if you can put them in a logical order in a logical structure. Even more so this allows you to easily give the correct access to the right people. So if you have a very large project, let's say build an operating system, you don't want to give everyone access to every single piece of the code. And by having these nested groups it makes it much easier to define this. You can for instance say everyone has access read access to everything but only write access to particular parts and it's easier to manage when you have like this. One example in particular are Android repositories. So you know Android the mobile operating system and if a lot of big companies are actually building on top of this or they're forking this for instance you know that if you buy a Samsung telephone you have not just stock Android on that like you get with Google's phones but you have Android with a few changes. So a lot of organizations are doing this and Android notoriously consists of many different repositories that are nested inside of each other and they created a custom tool to be able to stitch those together. Now that meant that they are not able to use GitLab or any of its competitors until March 22nd because from that moment forward you can actually use GitLab. So you can actually have 25 levels deep of subgroups before GitLab says okay no more which is enough to host the Android repository. Interestingly no one else is doing this so if you are looking for a Git hosting solution where you can have multiple groups inside of groups inside of groups GitLab is the only one that can do this. Super big news super super big news so this is a really big deal and I'm really excited about it. Next thing we're improving issue boards and we've been doing this very consistently the past few releases and this one is bringing a very big deal having the ability to actually reorder cards so issue boards as you know consists of multiple lists and until until March 22nd you're not able to reorder those and maintain the order of the cards and you will be able to do that now and in enterprise edition starter will allow you to associate a particular milestone to a particular issue board and that allows you to use issue boards in a more traditional sense so in a traditional sense you have a sprint this is how many people use Jira for instance you have a sprint where you say this is what we're going to do this week and it moves to certain stages and in GitLab you are now able to use a milestone to that goal and you can have a very traditional type of issue board of of can bend board as they say. What else we're bringing deploy boards to enterprise edition premium and deploy boards is a very cool feature that allows you to see how your deployment of a new change as you deploy to a particular environment progresses over all the different nodes so in you know in modern systems it's not just the single nodes that you're deploying to but you're deploying to the whole bunch of servers or better you're deploying to a whole bunch of containers usually managed by something like Kubernetes and we deploy what you can actually see how your deployments are progressing over that whole very cool feature. Then and this is a mock-up screenshot so I'm not sure if this is actually how it's going to look but as you should know we've been bringing Prometheus to GitLab and Prometheus is a monitoring solution it's very elegantly designed and it allows you to monitor all sorts of things but primarily you can monitor like performance like how is your system performing what is your system doing right now and we already brought it to GitLab with the previous release and what we're going to do now is that if you are using GitLab at all we'll enable it by default and we'll tell you in the environment whether what what the states of that environment is so you can see certain kind of metrics about your systems. Also in 9.0 we give you the ability to export issues and this comes to enterprise edition starter and it allows you to if you have a whole bunch of issues simply export them as like a CSV or like a excel format. It's very useful if you want to do some custom excel stuff with issues it's something people want and on that point GitLab 9.0 is the biggest release we ever did so I just yeah I took these features and I wanted to highlight them because I think they're all a very very big deal but besides them there are many other features that we included in GitLab 9.0 and incredible amounts of performance improvements as well a lot of small improvements like improvements to ID to production and making a few things just just that little bit better we're doing a whole bunch of UX updates for instance the merge request window will be a little bit better and it's just such a big release and bringing subgroups to GitLab is such a big deal it's hard for me to express even with my excitement how big of a deal this is and I want you all to share this enjoyment and I want you all to share this with everyone and bring out the word because it's such a big deal um but as is my job I have to always be looking forward so and what I am looking forward to now now that we basically finished 9.0 is GitLab 9.1 because that's how it goes so April 22nd we'll release a GitLab 9.1 and as always it will probably be a slightly better than 9.0 no matter how good that release is and a few things that we're doing we're bringing multiple assignments for issues which is something that some of the competition is doing and some a lot of people actually really want this and it simply allows you to have multiple assignments for an issue so you can say it's not just Job that should be doing this but it's Job and Sean for instance have to do this we're also working on and this was initially planned for 9.0 but we thought 9.0 is so full we can't possibly put this in anymore we're working on service desk and service desk is a very cool feature that allows you to basically do support straight from GitLab what that means is that if you have some support address like we have support at GitLab what you can do is you can point that email address to GitLab and then whenever a customer emails you at that address it creates an issue and if you then are a user in that GitLab instance you can reply directly to the customer's issue from within GitLab so you just reply you create you get an issue that says the customer says oh I want this and this or this is not working you can just reply to the issue like you would do normally and they get an email back and you can navigate like this and you can do things like have private comments it's an incredibly powerful idea to just eliminate all of support software and just do it in the same place that you're doing development I think it's an incredibly cool idea and the first iteration will ship with Enterprise Edition Premium in 9.1 hopefully and we're also working and this is I probably besides GitLab itself one of the longest running projects within GitLab but it seems that for 9.1 we're on on schedule to to ship this and highly available package product so that means that you can have highly available GitLab straight from the package straight from when you install it and that means that we pre-configure for instance a highly available database for you and that's also shipped with Enterprise Edition Premium another cool feature that we're working on and I by now I'm feeling that I can start to overwhelm you with the awesomeness so this is also one of the last ones is canary deploys and a canary deploys a really cool concept where you know instead of saying I'm gonna I have this change and I deploy it on my server see if they break and otherwise I reroll them really quickly I just deploy to one of my nodes or to a subset of my nodes see if they are working well and if yes then I deploy to the rest of the cluster I really like this idea it's a very powerful idea and I think the canary comes from the fact that you went into the mines you had a canary and if the canary fell off you have to quickly get out because he's more sensitive to toxic air than you are so a little little little deployment see if it falls down and otherwise you move forward and then I think this is the last one maybe second to last one burn down charts this one it's a nice design by Pedro it's been in the working for a while and it basically allows you to see how much am I on track in the current milestone so I have a number of issues if I were to take and I have a certain due date for this milestone if I were to draw a linear line from today until the due date descending the amount of issues that I still have to complete or the weight that I gave the issues how am I on track with that and like you see whether you're ahead of schedule or behind schedule whether the green line in this case is above or below the dotted line and this will come in enterprise edition starter and then this is last and I will never fail to mention this idea to production the idea that starting with just an idea and actually building that and shipping that to something that is live and that is running somewhere and making that easy to do is is the ultimate realization of what GitLab is supposed to be so making it easier removing small hurdles small thresholds to move between steps from going from idea to production whether it is you know making it easier to deploy or making it easier to make an issue every single one of those steps we should be continuously improving and we have done a number of those improvements in 9.0 and in 9.1 we have a whole more that we're going to add and a few of those are you will be able to create a working part against merge request straight from the issue page so that the threshold the step from going from an issue to having some sort of code or having a place where the code will be is basically one click will make it easier to navigate from and to the terminal so that if you want to try something out if you want to poke around in an environment that's easier to do if you want to you know quickly get started they use a template will make that easier to do will make it so easy that before you even have configured your project or when you are creating your project you will already have the templates automatically deploy will improve the metamos integration for instance that if you create a group inside of kitlab automatically in metamos a group is created so that if I am if I am interested in building something then immediately in metamos the people that I have involved in this project are there as well and even cooler automatically configuring kubernetes for a project so that I don't even have to think anymore about this kitlab ciem or no it just comes and it works as it's supposed to be so these are all very cool things some of which will lend in one so which will decide to do differently or move to another release but that is just to give you a small peek into the cool things we're doing in the future and with that are there any questions I should do the thing with a timer of 20 seconds I'll just chat here as well all right I'll start at the bottom set as will we detail the performance improvements and all the improvements since 8 to 0 in the blog post and the answer is yes and not just because you're my boss how soon after burn down charge will gain charge be implemented as wrap we don't know so we don't plan very far in advance we don't have any very concrete plans for gain charts it's it's kind of hard to do how big of a win is that compared to other things that we might have to do but it's definitely interesting and we know that someone created the community version for that something to to consider can I share these slides with Oracle yes you can you can also share another summary of 9.0 we'll have the blog post up soon again it can be yes of course what am I not excited about I'm excited about everything that's good let's see what else will we be dogfooding the service desk and move away from Zendesk well you know tools like Zendesk are very complex and there's hundreds of engineers working on those kind of tools and I believe we lose many of the features so I do hope that we find a use case on its very inception and we should dogfooding is always a good way forward but to say that we'll be moving immediately away from Zendesk would be a little bit early but I do hope that that is something that we can do in the future okay back to the bottom okay I think that was everything now I'll give you 20 seconds to ask a question actually you'll have a quick question about the godr alpha release I think it is for 9.0 is it I lost track of it is that indeed an alpha release for 9.0 I believe so I believe it's still on track as an initial alpha that doesn't mean that you know it's not yet easy to use we have to do a lot of improvements there and as an alpha it's not fully stable yet but we'll make sure to detail exactly in the blog post what the current status is and how it's going to look and also as an FYI because we have this feature freeze on the 7th of the month that means that tomorrow and I've heard from PMs that they're already working but in theory tomorrow we'll be starting and doing most of the blog post already and each PM will be writing their part of the blog post and I will make sure to share this in the team call as well so if you want to get a full overview of what's actually shipping all the details you'll be able to see that on a very very short term besides this presentation of course cool thank you so Phil asks can clients integrate their existing service desk vendor with this new offering or would they simply not use the server desk option so if you're using some other kind of support system the idea is that this replaces that in the long term in a short term can they integrate it unless we have an existing integration with GitLab with this then otherwise no now it wouldn't be possible of course you can use GitLab API to build all sorts of things and it's definitely something we should consider right making it easy for people to decision between tools is one of the things that we're quite good at we have really nice importers for various systems so it's something we can consider but it's very early days right first iteration we always keep it simple so we ship first first iteration of server's desk and then we'll see what is next and what is the next logical move and how people are using it actually thanks yeah yeah and it was just wondering you know what would the migration look like if they're already using Zendesk they would have to just straight get off Zendesk and come to our service and is this product big enough to compete against Zendesk right that type of thing yeah no those are really great questions obviously we won't be able to compete with a service that has been made for many many years with a single feature that we've made in a month so it will take a quite a long time before we can say well we are competing one-on-one with services like this so on the short term no and there won't be anything but it will already be useful and there will be use cases where people will say well I don't need this heavy handed approach of using Zendesk which has several other setbacks and I could just use this very lightweight alternative and on the long term we'll see maybe it makes sense to to have some sort of migration path it all depends on how the market responds and how we are continuing iterating on this and I wouldn't dare to predict the future without any data all right any other questions quite quite a few questions oh Ryan asked do a lot of people use metamos with kitlab it doesn't seem to come up that often for me in conversation so the chat market is a very interesting market right there's many offerings with most of them are commercial like slack reviews ourselves there has to be a place for an open source alternative and one of the things that we're doing is we're pushing that open source alternative with kitlab itself right so many of the things that we do like the chat ops kind of stuff that we build it works across metamos and slack and microsoft teams for instance in the near future but to do this very integrated out of the box experience the kind of things that we do with kitlab we wouldn't be able to do that if we were to use a paid solution so that's that's one of the reasons why we choose to use metamos and it's good that there's an open source alternative to the to the commercially available chat clients um let's see did I miss anymore all right no more questions three two one all right i'll see you all in the team call thank you for listening