 All right, it's 4 p.m. Scotland time, which means it's Almost completely dark outside. I'm Sean McGiven and the Discussion back-end team leads and this is what my team has been doing for the last five weeks Just before I share my screen someone mentioned on the blog that Sometimes my microphone hits my sweatshirt. So I've gotten the air gap at the moment But if anybody could tell me in the chat if that's happening that would be appreciated Because I don't want to do that right, so In this is actually been six weeks since my last update because I swapped with Dower last week So in 10.1 and 10.2. I'm gonna talk about some significant features We have commenting on image shifts, which is a really really really cool feature Now it's not just restricted to text that you can comment on but also pictures in your mode requests Which makes it much nicer to You know review designs, but also just like you know screenshots or documentation images you can Take a look there We have lock Locking for issues and merge requests to make it so that only team members can comment Which is quite nice for open-source projects as well. I don't think this is So useful for internal projects, but certainly for open-source projects. That's a really useful feature and in 10.2 we have save board configuration, which is Just a really cool feature as well It means that instead of just having a milestone saved to a board you can have Labels and other filters saved as well. So it's much easier to share that board with other people Also in 10.2, we are doing the first iteration of epics At GitLab we iterate on things We take that quite seriously, which means that the first iteration of epics will still be missing a lot of Features that we will add in future, but we want to get something out there and get it in front of people and start using it ourselves as well Essentially, these will hopefully replace the meta issues that we've been using where we just collect a bunch of issue links and put them inside an issue and give that a more More of a first-class feeling within GitLab itself These exist at the moment, not a project level, but only a group level And these are part of the portfolio management. We're working on in GitLab Enterprise Edition Ultimate Where we're going to add other features on top of these So higher level planning in future We had some team changes since last time Douglas has been on the Geo team Since like February but is now officially full-time permanently on the Geo team and Valerie has also joined him We have one person joining already at the start of December and we're hiring for another So if anybody knows anybody who's awesome, please feel free to refer them We'd already have some Some good candidates in the pipeline There are some immediate consequences to this just because we have fewer people right now Which is that we can't do the Rails 5 upgrade in 10.3 when we wanted to We'll take a look for 10.4 and see if we have capacity for that But otherwise it might be the start of next year before we can get that finally finished and elastic search improvements as well that will take a lot of effort and You know, it's it's the kind of thing that we should you know really focus on and do it right when we do it So we're gonna put that to one side for the time being in 10.3 We've got some cool features as well This has been requested for a very long time But basically at the moment if you add a comment on a commit and that commits part of a merge request You can see the comment in the merge request But then if you force push to that merge request so that the commit is no longer part of the merge request the comment goes away So if people For the GitLab workflow like that we use this is not a problem. We don't really comment on commits We comment on the merge request diff as a whole But a lot of people use commit work commit review workflow where they comment on commits Individually and it's really frustrating to them if that was so rebasing or amending those commits that You know those comments disappear. So we're adding The ability to make those comments tied to the merge request as well as the commit so that we can Keep them and make them resolvable within the context of the merge request We're doing a lot more work on epics and portfolio management We are adding some specs in GitLab QA for things that are hard to test in The main application itself. So GitLab QA is a separate project that can Do I guess black box testing this of a GitLab instance? So the reason protected branch is a tricky for instance is because There's a lot of moving parts when you actually make a commit either from the web UI or from a just you know pushing from your command line and We you know within the the rails application We don't have all those parts available So we have to mock them out and if we mock them out, obviously, we're not actually testing the full flow So it's really important to get back and get lab QA and then the final thing is my pet project which I've been working on for probably over six months now on and off which is to Change the schema of how we store changes in merge requests to make it better. It's It's I'm hoping to get that finished in 10.3 on gitlab.com. It's pretty much done So we just need to make sure that it works for other instances as well But we had a lot of data to migrate. So I'm pretty sure that other instances will be fine, too And once that's done That sort of solves a lot of or helps solve a lot of performance problems we had but also unlocks some features that we could have in future To actually introspect like how big merge requests are Which was completely impossible before So that's all I got Stop sharing my screen. I Don't see anything in the chat. So hopefully the air gap worked If anybody has any questions, I'm gonna give you 30 seconds by my phone's stopwatch. So Ask if you want otherwise You just wait a few more seconds Yes, Bobby says nice and concise. I think if you add together the total time of all my functional group updates I'm you know This is probably pretty low still. I don't I don't believe in there In I'm just not very interesting and I can't talk for very long without feeling incredibly self-conscious is basically it So that's 30 seconds. Have a great day everyone and I'll see you on the team call