 Let's start today. It's April 11th, I think. It is. I've been the warmest department of all of Europe and this is the product update. And the first thing I would like to mention and normally I talk about like future versions and all big things but for we after we released 9.0 we removed the left sidebar and people said that's such a big shame because I lost the ability to quickly see how many issues are assigned to me and how many pull requests are assigned to me. And we actually shipped this in a patch change and I'm very proud of the team. They moved really fast after having heard the criticisms about the sidebar and having lost this functionality. They came up with something new and we treated it like a regression and we shipped it in a patch release. I'm very proud and it's a very nice change and I love the colors. Also if there's zero there's no color there so it doesn't stick out too much. It's just great so I congratulate everyone that was involved with that. I also want to update on the technical writing team. They are also part of product nowadays and they do a lot of interesting things. So I want to highlight some of the things that they recently did. They added topics to the top of kitlab docs. So if you go to kitlab docs there's topics there and it really nicely puts together some information on topics that otherwise is distributed all throughout the documentation. For instance you want to know about kitlab pages. There's a really nice one for that there and you'll find the installation, the setup, the maintenance but also how to use it and it's just linked to other parts of the documentation. So we still maintain a single social truth but it makes it easier to find these things. Sean is working on a website conversational development about well exactly what it is called. I recommend you check it out. We're adding a whole bunch of comparisons to the comparison page. We're just adding Jenkins but there's a few coming up shortly. The index pages of documentation are being improved and updated so it's easier to scroll through things and the topics are actually good examples of this. And what we're finally doing is removing the table of contents that is now on top of the documentation to the sidebar at least if your screen is wide enough and you wouldn't believe how big of a difference this makes. The documentation can look very overwhelming with a huge list on top and now it will change. So much for technical writing. Good news is 9.1 is already done. On the 7th we close the milestone and we start to work on the next one. So we know actually exactly what's going to ship in 9.1 and one of the major things is service desk and what service desk is it is customer support straight from GitLab and I wanted to explain a little bit more in detail how that exactly works. The idea is that if you have a customer or not a customer potential customer or someone that wants to share something with you that is related to your service they can email a regular email address. So in GitLab there's an email address you can for instance forward that from a specific one or you can just share that one and customers can directly email to that email address and get email back from whoever's on the other side because what happens on the other side is that inside of GitLab a confidential issue will be created and everyone that is active on that issue all the responses there they will be automatically emailed back. So this is a very powerful way to have feedback, to have customers report or anything else that has some sort of interaction inside of GitLab without requiring people to sign up to your instance. It's a very very powerful idea it's very simple and it makes use of so many of the existing GitLab features that made it very easy to work on this. We have many plans for the future for instance you know what is glaringly missing right now is like a really simple email address but because we are building on older infrastructure we couldn't do that. It all comes in the future but this as it says right here works and I think it's just beautiful it just lowers the threshold to contribution to having people share something with you and you should check it to to the lowest possible way. Very cool. Another very cool thing is canary deploy so canary comes from the canary that they used in the coal mines for you know when the methane gas or the carbon monoxide was too high the canary would die and then you knew you had to get out because as a human you can withstand a little bit more of that but not much more and a canary deploy basically does that you do a single deploy or to one or a few containers instead of to your whole cluster if they pass if they work okay then you can decide to deploy the rest but if they fail then you have the option to just roll those back and not everyone is affected only if a set a subset of your users raises can be effective and very useful. Another one burn down charts burn down charts is best shown this is what it looks like it gives you an idea of how far along you are in a particular milestone so if I have a hundred issues and I have a hundred days that means that on average I have to close one issue a day in order to complete the milestone and a burn down chart will give you exactly that it will show you the line you see here straight in your line that says this is approximately how you should do it and it gives you the actual line of where you are and where you've been. It's a much requested feature it's very heavily used in agile teams and this is an interesting one so we made it easier to access templates imagine how it's not a big change it's very minor but the thing is many of the magical powers of GitLab rely on templates for instance creating a docker file or using auto deploy that's all based on templates and up until recently what you had to do is you had to type the file name before you get to show the template drop down now that's that's a very elegant solution but we want to encourage people for instance to create a GitLab CI file and it's very easy to mistype when you type dot GitLab CI YAML well that's no longer the case you can just find the template in the drop down and you can easily click it so we hope this encourages people to create more CI YAMLs create more Git ignores etc etc this should make it easier for everyone. I also love this gift it's like so satisfactory to look at this and there's a whole bunch of other cool improvements and this is not even nearly all of it but just to mention some of them we now have recent searches in the issue search bar so if you have very complex queries you can just click them just local storage so it's very very fast the merge request widget has been updated in 9.0 even more updates in 9.1 there's a mini pipeline graph in the commit view so you can see exactly where your pipeline is this is to me one of the coolest things ever there's a mini promiscuous graph in a merge request widget so you can see what the current state is for instance of of memory we you can now restrict tag pushes before you could restrict to branches now you can do the same to tags one of those things that obviously we should have done it a long time ago nowadays in GitLab and and we can never stop mentioning this because it does require a lot of effort there's many performance improvements in GitLab we really make a very conscious effort effort to prioritize them we prioritize them over other things so it should be mentioned that it's extremely important the team has worked very hard to make GitLab faster in almost every way so that's awesome all right if you can see the small letters here it says 9.2 which is our next release which actually we've already started so yesterday we had the kickoff which is always the first way of work day after the 7th where we say okay this is what we're going to do next and what I forgot to include here but I should share with you is that we created the blog post already of GitLab 9.2 so you can already look at the blog post and what we're going to ship on May 22nd I think that this is really cool idea by Zid and it worked out but I'm going to summarize some of the cool things here one of the coolest things and I was checking out the issue and Mark has made it very humble saying you can link between project pipeline fuse but what this really is is that this is cross project pipelines the ability to say if this project's pipeline is done then trigger this one or this one is required for this one or what it actually means is that you can now have pipelines to span multiple projects so if you have a project that has multiple dependencies those dependencies can then trigger a rebuild of that project and you can see that and here's a screenshot there's a lot of screenshots available in the issue it's for enterprise solution premium and it's such a cool thing this is the future right GitLab itself is like this we have many different dependencies they have to all work come together and once they're all together we have to put it all together and test that now we can now actually do that very visually or we will be able to do that very visually within GitLab with native support for that there's many additions and changes and requirements for us to fully implement cross project pipelines but this is a very good start so I'm very very excited about that and I think once this is released everyone will be very happy with it another one is and it seems minor but it's so it's such a big change in the product is that you can have multiple assignees for issues and this will be an enterprise edition starter it's just that it sounds very very simple you can just assign multiple people but it actually affects almost every single view in GitLab right so everywhere where you see this person is assigned we have to now be able to say these people have been assigned and it can be you know it can be one person can be two but it can also be 90 and we have to account for that so uh very excited about that we've been working it already for a while so it will definitely ship very cool another one and I can't really show you this because we're still working on the final UX for this iteration and that is the related issues so in GitLab things are already automatically linked up but sometimes you want to make a relationship explicit and the very look we we're always looking for the smallest iteration and in this case the way we do it is use just explicitly announce these two issues are related and it will be an enterprise edition starter in the future the intent is of course to be able to say the nature of a relationship to say this issue blocks that issue or this issue is blocked by that issue or etc you know these kind of relationships but there's a small starter first iteration we say okay you can formally say now whether issues are related and it makes management of very complex and large issues somewhat easier and then another one and I think this is also so cool so you can right now if you deploy your application from GitLab to Kubernetes you get all these cool Prometheus metrics that you see them in the environments page you see like oh this is memory and this is performance but what you really want of course is have any kind of metrics so with this change it will allow you to have your own metrics that you configure in Prometheus appear inside of GitLab so you could track whatever you want is it could be business metrics it could be any kind of metrics coming from your application or your server and they will be visualized in GitLab super cool and then lastly and this is a big one we're starting to translate GitLab translating a large application and many many different pages such as GitLab is a very very intense very complex process so we're doing as always the smallest possible thing we're taking the cycle analytics page and we're saying okay we're going to translate this or at least prepare for translation and maybe add one or two translations that is what we're going to do this release and then we hope we are going to continue continue this work over many many releases and of course hope that the open source community will help us with this but this is a big stop a big big start of this and a very big deal I would say because you don't see these very often that applications as big as complex in the market is we are are also translated but I think it's very beautiful because it will allow everyone to use GitLab you know without too much problems if you don't speak perfect English you can still understand what pipelines actually are because otherwise that word seems very strange at least to me and that's it let me know if there's any questions I'll also check this chat stop sharing mark says martin bell says is our support team using service desk now they are not yet but I know that Victor already created an issue for us to dog food service desk to start using it but server desk is not live yet on gitlab.com so because we all use gitlab.com we have to wait for it to be live so this effort is passed we're done with developing but now we have to create the initial release candidates do the testing and once a release candidate is live we can start using service desk all right I'll give you 10 more seconds by my pure guessing of 10 seconds I mean this was a long presentation you gotta have at least one question is Dutch the first language it is my first language I don't know if it will be the first language to translate to I think that what we'll actually do is right now in gitlab when you look at the page most of the strings are hardcoded so in the code we actually say button or okay or or verge and what we have to do is we have to change that and reference it to an external file and depending on your language setting that file has to be English or German or Dutch so that will be the first step so maybe the first language will be actually for sure it will be English maybe the second one will be Dutch but it all depends on who's implementing it or Flemish I'm Dutch so I think grammatically they are the same Spanish and German are the first two says Mike ah that makes sense all right my your 10 seconds are way over thank you everybody for listening and see you in the team call