Skip to content

TW group change tasks for GitLab Delivery / Self Managed and GitLab Delivery / GitLab Build

Use this template to manage changes when there is a new stage/group, a deprecated stage/group, or when a group moves to a different stage.

Related Issues, MRs, Links

Tasks for assigned technical writer

  • In the www-gitlab-com repository:
    • Check that an update for data/stages.yml is in progress, and link the MR to this issue. A group or stage change is usually initiated by a Product Manager or Engineering Manager, who is responsible for following the process for Changes. It the PM or EM's responsibility to raise the MR to update stages.yml.
    • Once the stages.yml MR is merged, check that the changes are reflected in Assignments to DevOps Stages and Groups. The assignments table automatically pulls in the data from stages.yml. There should be no additional action required.
  • In the gitlab repository, update as needed (in the following order, but can be done in the same MR):
    1. The metadata in all related markdown files.
    2. Group assignments in lib/tasks/gitlab/tw/codeowners.rake.
    3. .gitlab/CODEOWNERS by running the tw:codeowners Rake task to ensure no pages are missed.
  • In the Technical Writing project, update the Milestone Planning template.

Tasks for technical writing manager

  • Update the TW Tableau dashboard.
  • Update google sheets used for team rebalancing planning.
  • Check Workday for the Job Title Specialty (Multi-Select). If the specialty does not exist, create an issue in the People Group general project, and use the Workday: Job Title Specialty Request template.
  • Update Workday with the new group assignments. Log a HelpLab Job Title Specialty Change request for the People group to update Workday with the new group assignments. Workday updates the group assignments in data/team_members/person.