Verify Stage Category Review FY23Q4
Purpose of this issue
It is audit time According to our handbook, There are a maximum of 8 high-level categories per stage to ensure we can display this on our website and pitch deck. (Categories that do not show up on marketing pages show up here in italics and do not count toward this limit.)
For groups that have two or more categories, but not all categories in a stage, the group name must be a unique word or a summation of the categories they cover.
Group | Category | Maturity | DRI | Marketing (Y/N) |
---|---|---|---|---|
Pipeline Execution | Continuous Integration (CI) | Complete | @jheimbuck_gl | Y |
Pipeline Execution | Merge Trains | Viable | @jheimbuck_gl | Y |
Pipeline Execution | Continuous Integration Scaling (CI scaling) | Minimal | @jheimbuck_gl | N |
Pipeline Authoring | Pipeline Authoring | Viable | @dhershkovitch | N |
Pipeline Authoring | Jenkins Importer | Viable | @dhershkovitch | N |
Pipeline Authoring | Secrets Management | Minimal | @dhershkovitch | Y |
Runner | GitLab Runner Core | Lovable | @DarrenEastman | N |
Runner | GitLab Runner SaaS | Viable | @DarrenEastman | N |
Runner | Runner Fleet | Complete | @DarrenEastman | N |
Runner SaaS | GitLab Runner SaaS | Viable | @DarrenEastman | N |
Pipeline Insights | Code Testing and Coverage | Viable | @jocelynjane | Y |
Pipeline Insights | Performance Testing | Minimal | @jocelynjane | Y |
Pipeline Insights | Review Apps | Complete | @jocelynjane | Y |
Pipeline Insights | Build Artifacts | Minimal | @jocelynjane | N |
Action items (follow ups) from this issue
- MRs for proposal for category changes (add/remove/rename/consolidate), see example: Renames Users Category to User Profile (www-gitlab-com!100978 - merged)
- New group level direction pages, see example: https://about.gitlab.com/direction/create/editor/
-
Why is Continuous Integration Scaling (CI Scaling) a category? What makes this different from CI? - @jheimbuck_gl -
Why is _Pipeline Authoring _ a non marketing category? - @dhershkovitch -
Pipeline Authoring needs to be renamed as it violates "For groups that have two or more categories, but not all categories in a stage, the group name must be a unique word or a summation of the categories they cover." - @dhershkovitch -
Should Jenkins importer remain a category? Are we investing in this? - @dhershkovitch -
GitLab Runner SaaS appears twice - once under the Runner Group and once under the Runner SaaS Group - @DarrenEastman -
Should any of the Runner categories be a marketing category? - @DarrenEastman -
Why do build artifacts belong to pipeline insights? - @jocelynjane -
Pipeline insights- do all the categories under PI make sense? Are we investing in each category?- @jocelynjane
Proposal
here is my proposal for categories to move into maintenance mode for FY24:
- Merge Trains
- Build Artifacts
- Code Testing and Coverage (already done)
- Review Apps (already done)
Please add a disclaimer to your direction pages and add me as reviewer. We also need to move out category maturity dates.
Let's submit MRs to remove the following categories:
- Continuous Integration Scaling (CI scaling) - Why: This is foundational to CI and now that we have a Tiger team for this a dedicated product category is no longer necessary. MR
- Jenkins Importer - Already in progress
- Performance Testing - Already in progress
The categories we will be adding/revising:
- CI Catalog (WIP)
- Code Testing => Test Intelligence (WIP)
- Build Analytics/Visibility - Why: we need a specific direction on how we will enable users to report and see Pipeline/Job performance - @jheimbuck_gl, WDYT about getting a direction page going for this?
Categories with Theme Alignment in FY24:
- CI catalog
- Pipeline Authoring
- Secrets Management
- Runner Core, Runner Fleet, Runner SaaS
- Continuous Integration (CI) - CI_JOB_TOKEN, Pipeline Performance
- Build Analytics/Visibility