 Okay welcome to the last tutorial of day one. Happy to have Jackie talking about the GitLab release stages. So without further ado, Jackie, I'll turn things over to you and you have thanks for putting those slides together and tell us everything you want to tell us about release and how community members can help. Awesome. Thanks Ray for the intro. Well as a foundation release management is within the ops section of GitLab meaning it is the portion of the life cycle where people are packaging and releasing their software. So there's some key features and key pieces of release as a part of this product spectrum. These include continuous delivery, release orchestration, pages, review apps, feature flags, release evidence and secrets management. When we think about the three-year vision for the release stage it's composed of those two major areas of release management and progressive delivery. Under release management I'm the person who owns that vision and my team is really working to empower all organizations to effectively deploy their software when, where and how they want to while supporting a natural secure and traceable process. The things that I'm focusing on this quarter and for the rest of the year are mostly in the release orchestration and secrets management categories within release management. Progressive delivery is doing a lot of really cool work around continuous delivery especially when it comes to advanced deployments using something like feature flags and our auto deploy templates within auto DevOps. When I look at the areas that we've developed in the past year or so their key features are around the releases page and piece of that is also displaying environments and the environments dashboard. This is where the community could really help improve our releases page experience by enabling more features and parity within the releases page from our competitors. So for example we have a lot of features around assets and publishing releases that would be really useful to start getting more enhancements on. When we look at how to navigate and where you can contribute there's a couple of different filters that I have to make it really easy. One of them is accepting merge requests. So any issue that has the flag accepting merge requests and is in the ready for development column will allow our developers to just pick up and then we're ready to review it. There's a couple of features around permanent links to the latest version of release and automatic insertion of changelogs into releases that are really exciting for our users. Additionally when we think about empowering organizations and empowering developers to release their binaries, distribute those binaries there might be a case where they want to publish those releases on the release page without giving access to the source code. So this feature would be a really great opportunity to help enable a bunch of users to better leverage GitLab releases like they would be using GitHub releases for. We also have a couple of other enhancements that we're really looking forward to potentially getting built into the solution including chat notifications when deployments start, web hooks related to deployments are a really great way to create automation around your releases workflow and we have a lot of users that would be really excited about having these features built natively in the GitLab. We also have some low hanging fruit features where if you have a label on an issue that says low hanging fruit these are typically weighted with one MR or less and they may be a feature or a bug. Some examples of these are going to be enhancing buttons or conforming to a button style in the front end or potentially implementing GraphQL endpoints. So if you're excited about using GraphQL and instrumenting those endpoints we have several of those issues in low hanging fruit. That kind of concludes exactly where we're looking to direct people to help contribute to the release management functionality and stage. On a process side any of these features that you look to develop it'll go through a review cycle with one of the developers on the release management team. Our idea is to prioritize community contributions and get them merged in as quickly as possible. So the team is really excited to potentially have a lot more contributions in release management for them to review and work with the community on. Ray, that's about it. Any questions or any areas where I should further dive into? No, I mean yeah thanks for this. I mean this is a nice overview with a lot of info on the slides. The other label that we have is we have a label called Good For New Contributors. You have the low hanging fruit with the level of difficulty but that might be something that you might want to add on some of the issues like working with the engineers on the team because one of the things I do tell a lot of the community members is just to look for issues with that label. So that might be another one that you may want to look at. Perfect. I can definitely look at our accepting merger question issues and kind of filter on more simple issues that we're expecting to be delivered with a low level of effort and kind of a fix that label to it as well. Right and then I'm going to share my screen as well. Hopefully you can see this. I was just looking at the MRs that are sort of in progress from community members on their release management stage. It looks like we have like a lot of them in flight and I mean good news is that most of these have been open in the last couple of weeks so we don't have anything that's been sitting around for a long time waiting for a reviewer and yeah and then it looks like we have like 30 38 that's merged already. It's already seeing good community contribution and activities which is great. So and I'm really glad you pulled up the open ones because that timestamp is really important. We do try to prioritize this and get these community contributions merged in ASAP. Right. Right. Now I mean some of these I mean even like what I find is that even documentation one I mean these aren't like necessarily trivial. It requires some back and forth in a lot of cases but yeah I mean I would just I mean in some stages like I we see like MRs it's been open for like months but I don't see any of that in in release management so kudos to all of you folks on the release management team but this is awesome. So I mean I guess sort of the related questions I mean do you like as a team get together and and look at what's on what's open and and make sure they're progressing or like everybody's just being good corporate citizens but. So typically I look at community contributions in the release stage weekly and kind of work with my EM to make sure that we have capacity accounted for so that we can make sure in any given month we have enough time dedicated to merge. What's great is that we have a convo on workflow where if we have issues that are ready for development we keep our whip limits pretty close so people can always prioritize these reviews making it really easy for the team to self serve. Cool awesome and then for people that are listening if it ever becomes an issue where you don't feel like you're getting the timely feedback or attention that that you like I mean feel free to ping either one of us Shaki or myself and I mean you can I mean what I tell people is that you know pinging anybody at GitLab is a fair game for issues and MRs like we're employees but we're also community members so people have any concerns about timeliness on on feedback just just let us know. Yeah and I would say we definitely had a had a case where one MR ended up hanging out for a couple of milestones and it just took a a couple of maintainer cycles to get that merged in so it definitely has happened to us in the past and the person contributing was really eager to get it merged in and it was definitely effective to ping everyone that you can on it makes makes a lot of sense to help lubricate it through. Cool awesome all right well thanks for your time Jackie and and for the the intro I mean what I'll probably what I might actually do uh you mentioned like in earlier slides you mentioned uh or so I might have her come back and talk talk to community members about progressive delivery so it's another good reminder. Definitely she has a lot of really cool features that people would are anxious to get and that they're available for community contributions too. All right cool awesome thank you Jackie and for the most part I think the Wi-Fi was was good for the presentation so glad we're able to plow through. Thank you. Yeah joys of working from home sometimes like you you can't take good Wi-Fi connection for granted. I know that is for sure. All right I'll have a good rest of your day and I'll talk to you again soon. All right sounds good thank you.