 Nice Christmas tree, I go It's beautiful. Isn't it getting ready for Christmas already? All right. Good morning. Good afternoon, whatever it may be depending on where you are on the sides This is our platform back-end update for February 27th for anyone watching at home the recording I'm now a man. I am platform back-end lead at good lab and now I'm gonna try to share my screen I think that means that I won't be able to see any of the cameras anymore So I'm gonna need you guys to Shout if anything breaks Let me see where did my presentation go? Okay. Can someone please confirm that the presentation is visible to you? Yep. Yeah, perfect. All right Right, so these presentations happens one happened one happen. Wow I'm tired. Sorry. These presentations happen once every five weeks. So to start let's go For the last five weeks Process-wise to be introduced in the last five weeks was to do a feature freeze on the seventh two weeks before the release of 817.0 on the 22nd Which means we had about two weeks to focus on getting regressions fixed before release Instead of after and better releases like we often did when we were still merging new stuff into the release two Three four days before and of course a lot of those things also introduced issues that we weren't aware of soon enough That's a major change for the last five weeks Of course, we released GitLab 817 with a number of these regression fixes and also a couple of Notable mentions that I've listed here. I'm sure you've all seen the retrospective or at least read the GitLab blog post GitLab 817 blog post. I'm not gonna go over these in detail But these are the major efforts that we as back-end platform were working on So now what are we gonna work in the next five weeks? First we will have Bob van Landijk, a new developer from Belgium joining us on March 6th Might actually be seven, maybe I messed it up, but at least one of those few days of March He used to work with Tone before they worked at a company in Belgium and now they both decided to join GitLab So it's gonna be great too. I'm guessing it's gonna be great for them to be reunited and I'm very happy to have them join the team Second we will likely start using separate milestones for development and the release Which is something that I proposed last week and that has been discussed in some issues But I think that at this point we have come to a conclusion that is not too controversial because initially I Proposed moving the extra release from the 22nd to the 14th, which was as I could have expected met with some Some doubts, but we will probably split up the milestones in the next five weeks probably for 9.1 On the 22nd, we will release GitLab 9.0 with first exporting issues as CSV This is something that customers for whatever reason are really excited about. I think spreadsheets Well, if you really want your issues in a spreadsheet that indicates that Don't do what you want to do. I need to improve GitLab But this is something that keeps coming back as a feature request. So we're gonna do it There's been a bug in GitLab for ages where if you delete a user It will also delete all of the issues and all of her comments and everything So it's a hard to lead which means that some really, you know useful issues and merge request and whatever are now gone This is something that's also going to be fixed with 9.0 instead of deleting all of these issues They will be assigned to a new ghost user that is used for all deleted issues So that we don't lose that valuable information Of course, you know the connection between your original author and that issue will be, you know lost So if someone wants to remove their trace and GitLab, they can do it like this and no one will know anymore that they offer some issues Third, we are going to ship impersonation tokens. This is a feature requested by a big Prospect and the idea is that in some cases they have automations like systems machines that need to act as if they were a certain user Right now the only way to do that is using the API is to Authenticate as an admin account and then pass a header that says I want to access this user But that means that this this machine or the CI built or whatever that needs to act as the user Needs to have access to an actual admin account from GitLab And of course the admin accounts API token is incredibly powerful and you don't want to just you know put it on a machine somewhere So these impersonation tokens allow an admin account to create an access token for a user that the user can not Themselves revoke and the idea here is that these can be used by these kind of automated systems that are set up by these admins To hook it up to you know internal tooling that kind of stuff Fourth, we're gonna ship API v4. This is an effort that started with 817 Multiple people have been working on this we shipped an API v4 beta in 817 because we don't want to miss any of the things We want to put in that for a 9-0. It's actually going to be ready. It's got a bunch of You know changes about the API structure to make it more consistent across the board It's got some some some other changes that will just make it slightly more useful to use It are backward and compatible so we cannot just change them in v3. That's going to be with 9-0 Work is also continuing on geo disaster recovery with 9.0 We expect to launch an alpha alpha version and we are gonna work with some select customers We want to kind of give it a try and see if we can can find some Issues that we want to iron out before this goes into a general availability. So with 9-0 We we want to put this in front of customers and then kind of make it more robust before we announce the whole world That this is now a thing we support Six is nested groups. This is something that pretty much was built by Dimitri our CTO himself Overcourt of like two or three months. He started working on it a couple months ago doing change little change by little change Because this is a really big change in GitLab to allow a nested like groups that are nested inside each other which means that all the routes have to change the URLs will now includes a Variable number of like namespace paths. So you can have for example like GitLab slash marketing slash About the GitLab.com for an example And this has very very big implications on the entire code base, which was never prepared for this And now needs to be but this is pretty much ready and we're just doing some latest last minute UI improvements that kind of stuff That's definitely gonna go in 9-0 and it's gonna be a really really awesome feature that customers have been asking for for a while So that's the 22nd on the 7th, which is in about a week We are gonna start development with 9-1 because like we did last month There's gonna be a feature freeze on the 7th, which means that after that date in the two weeks between the 7th and 22nd We're only going to add regression fixes security fixes that kind of stuff So all features for 9-0 need to be in by the 7th, which means that on the 7th We will start on features and they're like we'll get lab 9-1 The first thing we're gonna work on is numerous performance improvements We have these great performance dashboards which indicate like which endpoints are slow and what the 99 99th percentile is which means that this is the time that like 1% of people See this page is being this slow and in some cases that means 23 seconds or more of load time of some of the shuts in endpoints, which of course is something we want to work on We were hoping to work on this a little bit with 9-0 already But because we have so many breaking changes that we need to get out the door now because if we don't we will have to wait You know eight nine ten months or however long it will take to reach 10-0 We wanted to get those first and then we will get the performance improvements if we have time Chances are we won't have time for money of many of those for 9-0, but we will for 9-1 and we're gonna mark those as deliverable We're gonna treat them like the high priority urgent Issues that they are Of course, there's also gonna be major features in 9-1. I don't exactly know what those are yet I've yet to talk to Mike about those Mike is our PM for the platform team But I'm sure it's gonna happen in the next few days and then probably in the kickoff, which is gonna happen on the 8th We'll be able to talk about what's gonna go into 9-1 for the platform side of things So that's the back-end platform updates If you have any questions you can ask them now, I'm gonna share my screen. Let's see if I can find the shortcut for that I'm not seeing anything happen yet Okay, cool. Awesome. Looks like it works Any questions anything that you were wondering about what's going on the platform side last five weeks next five weeks anything like that? If there's nothing for 20 seconds, I'm just gonna quit the call and I wish you all a great day 15 then five All right, great day everyone And I'll see the ones who work at GitLab in the team call in 22 minutes and everyone else is watching them from home I guess I'll see you in five weeks. Cheers