Delivery Group FY24 Q4 setup
Continuing on the same line and direction from FY24 Q3, we are looking at Q4 with a similar setup, with blurred lines between the two Delivery teams to bring the right expertise on the right project.
Release Management remains one of our fundamental duties and the Release Management rotations are already defined for the next three milestones.
FY24 Q4 Project <> Team Setup
While we work on creating the official OKRs and epics, we can already share a proposed Delivery Group setup for Q4:
Ensure shipping of fixes for security vulnerabilities within their SLA
We'll work on reducing Security and Patch Release time and preparation and leveraging Release Environments. DRIs for individual initiatives TBC.
Team:
Reduce Customer impact during Dedicated Tenant upgrades
We'll continue the work from Q3, and thanks to what we learned, we will bring to the current Dedicated Tenants zero downtime upgrade capabilities.
Team:
- @nolith (DRI)
- @jennykim-gitlab
- @rpereira2
- @vglafirov
- @dat.tang.gitlab (in a very minimal capacity due to RM commitments and planned PTO)
- @skarbek (no capacity for the first 6 weeks of the quarter as engaged in another Dedicated Effort)
Individual team kick-offs, plans for demos, and other ways of working for both teams will be discussed at a team level to make improvements based on retro feedback.
What isn't changing?
- As for the last quarter, we won't change any management reporting lines.
- The planned release management schedule is unchanged.
@gitlab-org/delivery please review this issue and raise any questions or concerns directly in a comment or with your manager.