Hello, everyone, my name, is sonia pazitney and I'm the interim director of quality engineering at gitlab, I'm here today as moderator of the retrospective for a recent 14.0 release to provide you with a summary of the notes added to the retrospective by team members across r d. I will share my screen for the slides, great, uh so I'll, be talking through four topics: praise for the team, what went well what went wrong and how we can improve.

So, firstly, what praise do you have for the team? It's important to us as part of our values, to say thanks?

So what went well, a few themes I'd like to highlight are the successful delivery of multiple breaking changes during this major release: tech, debt reductions, increasing adoption of the migration testing pipeline and continuing the vein of previous retrospectives. We also saw a great collaboration as a continued theme.

So then what went wrong? The mr reviews, workload at some points during the month can be overwhelming and we also had difficulties with being able to complete planned work due to other priorities. Overall, we saw some confusion. A few misses and unclear processes around breaking changes, deprecations and removals, and documentation specifically for major releases.

So then, how can we improve so we're trying to ensure planning is complete by adding a peer review step and considering scope when assigning weights to avoid underestimating chores that seem easy on the face: we're also working on better documentation of processes and tasks, so that team members can go on leave without impacting team goals.

So thank you for listening to my summary. I hope you'll join me when we meet as a team for the retrospective discussion, wednesday july 7th at 1600 utc. We do have two discussion topics planned. The first is around ways that we can surface upcoming, license renewals for tools we use, and the example given here was around jetbrains ide.

The second topic covers the uncertainty. Some folks felt around committing breaking changes during the milestone and when that code would be deployed to gitlab.com, there will be a separate retrospective, specifically around major releases and how to better, prepare for 15.00 and beyond, given how different these can be from regular releases. So any ideas raised during the discussion will get funneled. There have a great day. Thank you.