Commit b1263e76 authored by Amy Shiel's avatar Amy Shiel
Browse files

Updated Dedicated labels to new group:: and devops:: labels

parent 2212baf7

content/handbook/engineering/architecture/design-documents/cells/infrastructure/_index.md

+1 −1
Original line number Diff line number Diff line
@@ -477,7 +477,7 @@ The first distinction is between teams implementing and maintaining the tools, a 
|                                                   | Emergency brake: stopping a package rollout               | team::Delivery-Deployments      |

| Rollback capabilities                             |                                                           |                                 |

|                                                   | Rollback with downtime (for QA Cell in ring 0)            | team::Delivery-Deployments      |

|                                                   | Delayed Post Deploy Migrations for rollback support       | team::Environment Automation    |

|                                                   | Delayed Post Deploy Migrations for rollback support       | group::environment automation    |

| Observability                                     |                                                           |                                 |

|                                                   | Cell health metric                                        | team::Scalability-Observability |

|                                                   | Fleet health metric                                       | team::Scalability-Observability |

content/handbook/engineering/infrastructure/platforms/project-management/index.md

+2 −2
Original line number Diff line number Diff line
@@ -102,8 +102,8 @@ The Infrastructure Platform teams uses the following set of labels: 


| Description | Labels |

|-------------|--------|

| The section label | `devops::data_access` <br/>`group::GitLab Dedicated` <br/>`devops::gitlab-delivery`<br/> `devops::developer experience` <br/>`group::Production Engineering`<br/> `devops::tenant scale` <br/>  |

| The team label | `group::durability` <br/> `group::gitaly` <br/> `group::git` <br/> `group::database frameworks` <br/> `group::database operations` <br/> `team::Observability` <br/> `team::runway` <br/> `team::Foundations` <br/> `team::Ops`  <br/> `group::Self Managed` <br/> `group::build` <br/> `group::framework` <br/> `group::delivery-deploy` <br/> `group::delivery-release` <br/> `team::Environment Automation` <br/> `team::Switchboard` <br/> `team::US PubSec` <br/> `group::developer tooling` <br/> `group::development analytics` <br/> `group::feature readiness` <br/> `group::performance enablement` <br/> `group::test governance` <br/> `group::cells infrastructure` <br/> `group::organizations` <br/> `group::geo`|

| The section label | `devops::data_access` <br/>`devops::GitLab Dedicated` <br/>`devops::gitlab-delivery`<br/> `devops::developer experience` <br/>`group::Production Engineering`<br/> `devops::tenant scale` <br/>  |

| The team label | `group::durability` <br/> `group::gitaly` <br/> `group::git` <br/> `group::database frameworks` <br/> `group::database operations` <br/> `team::Observability` <br/> `team::runway` <br/> `team::Foundations` <br/> `team::Ops`  <br/> `group::Self Managed` <br/> `group::build` <br/> `group::framework` <br/> `group::delivery-deploy` <br/> `group::delivery-release` <br/> `group::environment automation` <br/> `group::switchboard` <br/> `group::us public sector` <br/> `group::developer tooling` <br/> `group::development analytics` <br/> `group::feature readiness` <br/> `group::performance enablement` <br/> `group::test governance` <br/> `group::cells infrastructure` <br/> `group::organizations` <br/> `group::geo`|

| Scoped `workflow-infra::*` labels | (see below) |

| Optional Scoped `Service` labels | `Service::*` |

content/handbook/engineering/infrastructure/team/gitlab-dedicated/_index.md

+4 −4
Original line number Diff line number Diff line
@@ -378,7 +378,7 @@ When creating a new issue: 


1. Add the appropriate project label, example: ~"Hosted Runners for GitLab Dedicated".

1. Add the ~"workflow-infra::Triage" label.

1. Add the appropriate team label, example: ~"team::Environment Automation".

1. Add the appropriate team label, example: ~"group::environment automation".

1. Ensure the issue is confidential.

1. Add the issue to the correct Epic.
@@ -389,7 +389,7 @@ When creating a new issue: 
# Label with a project label.

# /label ~"Hosted Runners for GitLab Dedicated"



/label ~"team::Environment Automation" ~"workflow-infra::Triage"

/label ~"group::environment automation" ~"workflow-infra::Triage"

/confidential

```
@@ -541,13 +541,13 @@ To reduce the team's cognitive load on having to keep a mental record of all the 


Commonly used labels are:



1. The team label, such as `team::Environment Automation`.

1. The team label, such as `group::environment automation`.

1. Scoped `workflow-infra` labels.

1. Scoped `component` labels.

1. Scoped `cloud-provider` labels.

1. Scoped `workaround` labels.



The `team::Environment Automation` label is used in order to allow for easier filtering of issues applicable to the team that have group level labels applied.

The `group::environment automation` label is used in order to allow for easier filtering of issues applicable to the team that have group level labels applied.



#### Epics labels

content/handbook/engineering/infrastructure/team/gitlab-dedicated/environment-automation.md

+1 −1
Original line number Diff line number Diff line
@@ -21,7 +21,7 @@ To engage with the Environment Automation team: 
- [Create an issue](https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/issues/new) in the GitLab Dedicated team issue tracker

- Label the issue with:

  - `workflow-infra::Triage`

  - `team::Environment Automation`

  - `group::environment automation`

- When creating an issue, it is not necessary to `@`mention anyone

- In case you want to get attention, use a specific team handle (Ex: @gitlab-dedicated/environment-automation ) as defined in [Dedicated group hierarchy](/handbook/engineering/infrastructure/team/gitlab-dedicated/#gitlab-group-hierarchy)

- Slack channels

content/handbook/engineering/infrastructure/team/gitlab-dedicated/switchboard.md

+4 −4
Original line number Diff line number Diff line
@@ -27,7 +27,7 @@ To engage with the Switchboard team: 
- Label the issue with:

  - `component::Switchboard`

  - `workflow-infra::Triage`

  - `team::Switchboard`

  - `group::switchboard`

- When creating an issue, it is not necessary to `@`mention anyone

- In case you want to get attention please use the specific team handle, `@gitlab-dedicated/switchboard`, as defined in [Dedicated group hierarchy](/handbook/engineering/infrastructure/team/gitlab-dedicated/#gitlab-group-hierarchy)

- As a cross-functional team Switchboard uses `@gitlab-dedicated/switchboard/frontend-engineers` and `@gitlab-dedicated/switchboard/backend-engineers` internally to seek input from engineers with specific expertise
@@ -70,7 +70,7 @@ The outcome of the call is shared in a persistent location (Slack is not persist 


#### Resources



- [Switchboard team roadmap](https://gitlab.com/groups/gitlab-com/gl-infra/gitlab-dedicated/-/roadmap?state=all&sort=start_date_asc&layout=WEEKS&timeframe_range_type=CURRENT_QUARTER&label_name[]=team::Switchboard&progress=COUNT&show_progress=true&show_milestones=false&milestones_type=ALL&show_labels=false)

- [Switchboard team roadmap](https://gitlab.com/groups/gitlab-com/gl-infra/gitlab-dedicated/-/roadmap?state=all&sort=start_date_asc&layout=WEEKS&timeframe_range_type=CURRENT_QUARTER&label_name[]=group::switchboard&progress=COUNT&show_progress=true&show_milestones=false&milestones_type=ALL&show_labels=false)

- [Switchboard team top-level epic](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1048)

- [Switchboard team issue board](https://gitlab.com/groups/gitlab-com/gl-infra/gitlab-dedicated/-/boards/4498935?label_name[]=team%3A%3ASwitchboard)

- [Switchboard technical writing board](https://gitlab.com/groups/gitlab-com/gl-infra/gitlab-dedicated/-/boards/7068209?label_name[]=component%3A%3ASwitchboard&label_name[]=Technical%20Writing)
@@ -170,7 +170,7 @@ Switchboard team process to refine issues: 


1. [Switchboard team top-level epic](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1048)

    1. Look at the Switchboard top level epic and offer to work on issues with the nearest due date

    1. Use the [Switchboard team roadmap](https://gitlab.com/groups/gitlab-com/gl-infra/gitlab-dedicated/-/roadmap?state=all&sort=start_date_asc&layout=WEEKS&timeframe_range_type=CURRENT_QUARTER&label_name[]=team::Switchboard&progress=COUNT&show_progress=true&show_milestones=false&milestones_type=ALL&show_labels=false) for guidance

    1. Use the [Switchboard team roadmap](https://gitlab.com/groups/gitlab-com/gl-infra/gitlab-dedicated/-/roadmap?state=all&sort=start_date_asc&layout=WEEKS&timeframe_range_type=CURRENT_QUARTER&label_name[]=group::switchboard&progress=COUNT&show_progress=true&show_milestones=false&milestones_type=ALL&show_labels=false) for guidance



1. `Open` column on the [issue board](https://gitlab.com/groups/gitlab-com/gl-infra/gitlab-dedicated/-/boards/4498935?label_name[]=team%3A%3ASwitchboard)

   1. Look at the issues at the top of the `Open` column
@@ -387,7 +387,7 @@ Demo Link - see https://handbook.gitlab.com/handbook/engineering/infrastructure/ 


<!-- STATUS NOTE END -->



/label ~"team::Switchboard" ~"workflow-infra::Triage"

/label ~"group::switchboard" ~"workflow-infra::Triage"

/confidential



```