 Okay, hello everybody. It's I Have loaded the wrong functional group update here. So let me just fix that. That's the one from January So it's the 15th of February My name's Sean McGiven. I'm the engineering manager for the discussion back-end band at Gillab And this is what we've been up to lately On the portfolio management side, we've added a bunch of stuff This is probably the coolest one to show in a screenshot It's a roadmap view of your epics with their start and end dates. So Thanks to Jan and Kushal for working on that We have a really cool community contribution It's probably my favorite community contribution that I can remember since I joined Gillab, but I might be missing something even cooler Anyway, this one's really cool Now in a commit page it links to any merge requests that contain that commit so Most faces that's one but if you have multiple merge requests for the same commit to different branches It will show you those there, which is really nice because it's super easy to get backwards and forwards and look at the The review that happened around that commit and that was a great contribution from a community member here Are you key Sato? So thank you very much. How are you key for working so hard on that? We've been working on Uploads to object storage um We mentioned that Last time we have now Started to like this is deployed, but there have been some issues We are getting there. I've listed some issues out there Camille has also created a retrospective issue. So I'm gonna update the slides to link to that issue as well In future, but we are getting there and it's it's happening um Some performance improvements that I mentioned last time that weren't quite done The issues of merge request dashboard now will only time out when you don't search when you don't have any filters applied So when it's trying to show you all issues or merge requests across any project you can see I feel kind of bad that I'm talking about an improvement as the only timing out in one specific case But because it's one specific case That's good because then we can just say like we don't support that and Then it will actually perform properly in every other case So Felipe did a really great job there Global search also mostly doesn't time out anymore We still have a few cases where it does but he ended a great job Iserating on the the solution next we tried a few different things now we limits The amount of search results we will display or show to 1,000 because That's 50 pages at 20 a page and we don't expect people to be going through that many pages without narrowing it down We also improved the performance of the merge request widget polling. So when you're on a merge request page The widget is the thing that says like, you know merged pipeline status. It's got the approval status So when we pull for that in the back end, there's a bunch of Stuff we have to run And it was quite inefficient. It is now slightly less inefficient And I also made it so thanks Oswaldo for that. Sorry, and I also made a change which is mostly of interest to back-end developers I thought I'd mention it here Because it will help performance get better in the future in that it's now easier to profile a page and test those changes interactively in the Rails console because It's a it's a repel redeveloper in loops so you can You can make changes to the application and then profile those new changes inside the same interactive session Which is really nice for testing those changes and seeing how much of an impact they have other stuff Mario joined the team the The most notable thing he's done apart from help fix a bunch of specs Close to the freeze, which was really really helpful is Showing where notification email was sent So you might notice this in some emails you get now from GitLab It'll say that you receive this email not because of your account on GitLab But because you were assigned to the issue or something like that we're gonna add more reasons in future But that's really cool that we've started out in that it's both in the email body and in a special header We also have an API for search now. Thanks to Yaka for doing that. It works with the standard search as well as elastic search and When you're on the group issues a merge request page We now show issues of merge requests from subgroups as well as from this specific group, which is also cool So thanks to Yaka for that as well We're working on batch commenting for merge requests This is We were planning to ship in 10.6, but it's been bumped to 10.7 basically We need to do a front-end refactor here and it's it's quite a complicated refactor. So that's blocking The actual feature so the feature will be much easier to implement Whereas it would be very very hard to implement if we didn't do this refactor. So It's it's important to do but it is taking time For the day and fatty and Simon I will update the slides to mention Simon as well. They're all working hard on that Right now What's coming up more portfolio management stuff we're helping me in effort to Complete the GKE Integration stuff we're doing in GitLab We're adding an API for approvers and we are trying to reduce the load times for merge request diffs those are sort of the things that are top of my mind and I'm out of slides, so I'm going to check the chat So Yoke says Except merge request when build succeeds is his favorite. Yeah, I didn't realize that was a community contribution But it seems like ZJ did it before he joined in which case. Yeah, that's that's a strong contender because I Spend a lot of my day clicking that merge when pipeline succeeds So that's that's that's that's definitely had a big impact on my life. Thanks, CJ I'll give everybody sort of 15 seconds for questions. Otherwise We can get on with our day What am I most proud of recently shipping you personally? I don't really ship much except bug fixes I think as a team I'm really glad that we got the object storage refactor done It's Still not quite there, but I'm really glad that like, you know, we have refactored this We have decided where we can improve this in future We've identified those areas and we can We are very close to being able to start moving Uploads and LFS objects to object storage on gilab.com. So I'm really happy about that Um Brendan asks, is there any chance for a victor style quick feature video on roadmaps? I Can't do it now. I Can see if the team can do it. We actually have a weekly demo slash sync for Portfolio management, so I think there might be one recorded from there But if there's not I will see if we can record one and get that shared out Approvers API is coming is important to a large strategic customer of John mentions. Yep. Thanks. Thanks for mentioning that. I think it's It's good that it's important to a customer It's also been a gap in our API for a while that we have this feature with no API support So I'm glad that like we searched in this release that we're filling in those gaps and that we're making our API More of a first-class system. Oh, you're just gonna ask Victor to do it during his next week Which is even better because that means no work for me Awesome. Okay. Well, thanks for the questions and Have a great day everybody Enjoy the time until the team call