 Hi everyone. Sorry for the late start. I couldn't get into the meeting before. My name is Sean McGiven. I'm the discussion back indeed at GitLab. Just share my screen with the update of what my team and I have been doing for the last five weeks and what we'll be doing in the next five weeks. So in 10.0, we shipped some stuff, which is awesome. 10.0 being released on the 22nd of September, so a week and a bit ago. We shipped group issue boards, which fit from the previous release, which is awesome. I think everybody at GitLab who does any kind of planning or managing issues across a release really needed this, and it's awesome. So thanks to Felipe and Simon for that. We also have Jira Development Panel Integration for Commits. So as well as I was working on that, we hope to add other types of things that we can integrate into the Jira Development Panel in the future. But that's an awesome start. And Mikhail had worked on this before he joined GitLab and he finished it up in 10.0. That's a first-time contributor badge. So when you submit your first merge request to a project, you get a little badge that lets people on the project know that this is your first merge request and to be even nicer than you would be otherwise. We also have some community contributions on that subject. So one was to filter issues or MRs by your emoji reaction. So if you've added a star emoji to a bunch of issues, for instance, that you want to bookmark or favorite, you can filter by those easily now. We added a setting to when you push to a merge request, at the moment we follow the diff through for each comment on the diff and try and match it to align in the new diff. If it's outdated, we show it as outdated, but we don't automatically resolve the discussion. We make you do that manually because it's possible it just moved, but it still needs to be addressed. This setting lets you go to the other behavior of just resolving it if it no longer matches the new diff. We added a move quick action. So quick actions are etype slash and then move in the comment box and you can move an issue, which is super cool. And we got some time tracking information in the CSV export for issues, which is cool for people who like CSV exports. In terms of the team in general, most of them were at conferences this last weekend. So Yaka and Douglas, among other people from Get Lab were at Yiruku in Hungary. And Felipe on Oswaldo among others from Get Lab were at the conf in Brazil. So I've spoken to Yaka since then and it sounds like she had a great time and I'm sure Felipe Oswaldo and Douglas and everyone else who was there did as well. We've got a couple of concerns. Lock issue, I said here miss 10.0 and will be in 10.1. I'm still waiting to hear about that. I'm not quite sure what the hold up with that is, but it should be in 10.1 that freezes on the seventh. So we definitely have enough time to finish that. Valerie and Dimitri have been sort of working on the Rails 5 upgrade. Maybe not necessarily as a main project for either of them, but definitely as a thing they've been working on, but it's just not enough people. And the longer we leave it, the more we have to do because the rest of the team is busy adding new stuff that they then have to account for in the Rails 5 upgrade. So it's kind of a vicious cycle there. We'll try and get more people dedicated to that in 10.3 so we don't leave it hanging over our heads for too long because the longer we leave the existing MR, the more likely it is that it's going to be really, really painful to pick up again like if we left it for, you know, three, four months from now until we tried to get a team on it to finish it. It would take a lot of time just to get up and running again. So those are the two main concerns I've got at the moment. Next I've got two things that are pretty cool that are coming. So first of all is comment on images, which I bet both of these I hope will make 10.1, but I'm not 100% certain yet. So this is just you're in a diff view and you can comment on text and you can add discussions to the top level, but you can't comment on images or other files. So this is adding the ability to comment on a particular coordinates position by coordinates in the image and have a discussion thread on each of those coordinates that are selected. So that's looking super cool. Like I said, don't know if it will make it definitely in 10.1, but I certainly hope it will. And then another thing is saved board configuration. So this is really useful as well. At the moment you can only save a milestone on a board and then any other filters are added once you view the board. What this will let you do is save configuration to the board itself. So you can say that this board is for the CI CD team and anybody who loads it automatically has the CI CD label applied to their filters along with whatever milestone you pick as well. So those are two super useful things. I didn't include a last slide for questions. So I'm just going to go to the chat now and see what's up there. Yep, these are both cool features. Saved board configuration, like Europe said, especially is huge because it's like root boards. It's one of those things that helps us make boards better as well because we can actually use boards more and the more we use them because of dog fooding, the better we can make them. John asks if saved board configuration is a C or E feature. I think it is EES, but I am not 100% certain and Victor should answer that for certain, for real in the chat probably or on Slack because I don't want to give the wrong answer. I'll give everybody 30 seconds for any more questions. 30 seconds is quite an uncomfortably long amount of time to spend just staring waiting for questions but I'm done now. So thanks everybody. You've got 22 minutes back before the team call.