 YouTube afterward. So we had some troubles with YouTube possibly because of some settings in the live stream We don't know yet Emily said she's gonna take a look. So hopefully we'll get that sorted out and Also Yeah, so we can get started. I don't recall if we ever went through the team specific team retro notes But they're linked in the Google doc as you can see so teams can everybody can go go through those specifically and Read those and then we can actually talk about how we want to do this Retro in the future at the end of this call, which might be relevant previous retro improvement tasks again is more zoom troubles So I think Trevor left a note saying that he's going to take a look and so you can take a Peek at issue 185 in the people ops general project if you're interested But beyond that we can jump into it I see a lot of people clicking around but does anybody want to start talking or put on some notes into a one well this month If not, anybody want to speak specifically in their particular area and we can click through to Particular team So the plan team I did a lot of good things. So if you look at the plan link for the retro We shipped a good number of issues in 11.3 And a lot of them were we're good that ultimate features with with epics and for full management in general so I guess What I'm leading to is actually not me not not not the planning did a great job But it was often that the the production team and the team getting the releases out So I was really happy and I think all the folks are responsible for getting the RCs out early Was really amazing So so we had a good number of features that unfortunately didn't make it for 11.2 And they were pushed to 11.3 for portfolio management So it really sucked because we were really close, but we missed just missed a freeze But it also meant that those features were just merged During the you know the the like the red regression stage. I don't know what we call that those two weeks of After 11.2 free so they were already in master and ready to rock so Because we got our release candidates out so early at least users of gilab comm and in particular us We're able to enjoy those features really quickly So I think that was great. We're making huge strides towards continuous deployment from that perspective and so I Kudos to team. I think that went really well from the plan perspective or for that impact in the plan team So I'll leave a comment there in the agenda Anything else people want to bring up? Bob is just typing so might as well speak up Bob Yeah, so We had some patches that need to be applied to get lab comm during the full release cycle So that started somewhere around the first of them up until the 22nd We Remember those patches often, but just as often we forgot about them And then we had the release on the 22nd Which basically is our last RC that we tacked with the same version number a cosmetic release We call it so it looks like the same release that our customers are getting and so on and after that we Try to apply those patches, but something went wrong We didn't notice what happened immediately, but we continued with our weekend because it was a Saturday So that means that gilab comm remained unpatched Over the weekend and we only noticed on Monday that was going wrong. There's a Postmortem document about that which I'll link and which I'll dig up and link from from the main document here All right, if nothing else we'll jump to the final point Which is making this meeting a sink so you can click through I'll let Eric speak to whatever you're typing Yeah, I'll capture the notes after what what I think we should do is one engineering should should take over ownership of the other retrospective PM screw the own and run the kickoff so we can kind of divide and conquer there There's this trend of teams doing their own retrospectives That's really important because a good retrospective is like a psychologically safe space to you know in a nice way You know call someone out your teammate for something that they should have done But maybe maybe didn't do and when it's a broad meeting when it's streamed to YouTube I think people are holding back from doing that sort of thing and we're seeing that so you should formalize the the Individual group or team or retrospectives engineering managers run those record those in docs If they want to do them a sink great If they want to do them sink or in a scrape that have a dock either way and then this meeting should be about Transparency external to the company and internal to the company and I think what this meeting should become is you know managers coming here and and You know populating the stock with essentially the highlights from their individual docs That doesn't mean a little bit duplication of information, but I view that as curation like we're curating this like what what do people outside? The company want to understand about what's going on Of course we link back to those docs that people want to dive in And then this be this is still a synchronous and live-streamed meeting so that way it's again is serving that purpose Transparency and outward communication So I think I'm I've articulated that in the in the issue But thanks for creating that Victor and we'll run with that. I think our goal will be to If that's the plan lock it down if it needs to change change it but tape but in the next starvegy a month from now Perform whatever change or we're going to do and then that'll allow you to focus on the kickoff Great Did you want to assign somebody to that so unless you I don't mind running this meeting and just clicking buttons in YouTube? I mind when it doesn't work, but I don't mind Yeah, I think when I say take it over I mean like we do YouTube streaming issues someone If they're on vacation, they've got back up like full full ownership. I'll be right. Yeah, all right, so I will I Will so and then tell you tell me who it is. Should I just just forward Messages I already have someone in mind. I just want to have that conversation with them. But like okay tomorrow Yes, we'll have that person and they'll have 30 days to figure it out. Okay. We'll do. Thank you Do you want to wrap it up Eric any parting words for us? I? Think I think that's the big action item is let's You know, we made a bunch of changes this meeting I think those worked and now it's it's at another inflection point. So the big thing to do is to Sort of redefine the purpose of this meeting and change ownership and kick it off again All right. Hi everyone