GitLab Ultimate Rollout
## Goal Coordinate the phased rollout of appropriate GitLab Ultimate features across teams to improve planning, visibility and workflow. Everything here is just a draft, and open for discussion! I've just tried to put here what seems to make sense from a quick attempt to organize things. ## Key Contacts - Project Managers: @gaba @bella - Team Leads: @morgan @hiro @ahf @meskio @donuts @mikeperry @intrigeri @anarcat - TPA: @anarcat (highlighted independently from above because there are multiple overlapping sets) ## Timeline (High-Level) - **Month 1: [Discovery and planning](https://gitlab.torproject.org/tpo/team/-/issues/401)** Identification of priority features, document current usage, begin planning - **Month 1-2: Pilot**: Pilot key features (e.g. Epics, Scoped Labels) with 2–3 teams - **Month 3: Rollout**: Begin broader rollout, solicit feedback, adjust configs - **Month 4: Stabilization+**: Tuning, refining policies, documenting best practices ## Success Criteria **Adoption Goals** - 100% Current projects are actively using GitLab Epics and Roadmaps for planning - 80% of teams have at least one GitLab Ultimate feature enabled - Scoped labels are being used effectively **Visibility** - Dashboards used and useful to Project Managers - Security dashboards reviewed regularly - Project Managers have better overall insight into projects progress **Process and Documentation** - Internal docs and team training materials are published - Labels are documented so people know how to apply them - Teams and PMs report improved planning and coordination ## Todo - Link concrete issues to each Epic. For each feature, make issues and link it to the appropriate epic. - Once we have epics organized, we can use the Roadmap View to visualize rollout timelines, assign start/due dates to epics, group by milestones. - Coordinate feedback and iteration: each team should be encouraged to pilot features with a single project first; document problems/questions in the Epic; propose changes to global defaults/configs. Maybe we can use a recurring issue like "Feedback Round: Month X" under each Epic.
epic