GitLab has a broad scope and vision, and we are constantly iterating on existing and new features. Some stages and features are more mature than others. To convey the state of our feature set and be transparent, we have developed a maturity framework for categories, application types, and stages that considers both adoption and user experience. For a deeper understanding of the multiple dimensions that contribute to product success, please visit category health . We are present-day pessimists and long-term optimists and maturities will change, including changes to lower maturity rating, to reflect the bar we set for ourselves, our position in the market and for customers. Contributions from our community are an essential part of achieving this overall vision for GitLab.
Category
and
Application Type
maturity:
|
Stage lifecycle and recognition:
Product Investment methodology. |
GitLab features are grouped into a hierarchy, representing increasingly higher level capabilities. Features make up a broader Category, which then belong to a DevOps Stage. Stages are assigned a yearly lifecycle, and categories a maturity.
Since 2016 GitLab added:
Stage Roadmap:
Since 2011 GitLab added:
Stage Roadmap:
Since 2011 GitLab added:
Stage Roadmap:
Since 2012 GitLab added:
Stage Roadmap:
Since 2016 GitLab added:
Upcoming Categories:
Stage Roadmap:
Since 2017 GitLab added:
Stage Roadmap:
Since 2016 GitLab added:
Stage Roadmap:
Since 2018 GitLab added:
Upcoming Categories:
Stage Roadmap:
Since 2017 GitLab added:
Stage Roadmap:
Since 2019 GitLab added:
Stage Roadmap:
The maturity framework makes it easy to visualize where GitLab is making investments, and resulting category maturity improvements. As part of the planning process for each category, the set of features required and expected date to reach the next maturity is maintained. It can also be used to compare historical to planned velocity. A reduction in velocity is one of our biggest risks.
Below is a chart which illustrates the aggregate current and future progression of all categories.
Manage |
Stage Lifecycle: Usable for most GitLab users (typically year 4) |
||||
Category | Today | Q3 | Q4 | Q1 | Q2 |
Date | by 2021-10-31 | by 2022-01-31 | by 2022-04-30 | by 2022-07-31 | |
Subgroups | |||||
Audit Events | |||||
Audit Reports | |||||
Compliance Management | |||||
DevOps Reports | |||||
Value Stream Management |
Plan |
Stage Lifecycle: Users of other tools start to switch (typically year 5) |
||||
Category | Today | Q3 | Q4 | Q1 | Q2 |
Date | by 2021-10-31 | by 2022-01-31 | by 2022-04-30 | by 2022-07-31 | |
Issue Tracking | |||||
Time Tracking | |||||
Boards | |||||
Epics | |||||
Roadmaps | |||||
Service Desk | |||||
Requirements Management | |||||
Quality Management | |||||
Design Management |
Create |
Stage Lifecycle: Best product in the market (typically year 7) |
||||
Category | Today | Q3 | Q4 | Q1 | Q2 |
Date | by 2021-10-31 | by 2022-01-31 | by 2022-04-30 | by 2022-07-31 | |
Source Code Management | |||||
Code Review | |||||
Wiki | |||||
Static Site Editor | |||||
Web IDE | |||||
Live Preview | |||||
Snippets |
Verify |
Stage Lifecycle: Best product in the market (typically year 7) |
||||
Category | Today | Q3 | Q4 | Q1 | Q2 |
Date | by 2021-10-31 | by 2022-01-31 | by 2022-04-30 | by 2022-07-31 | |
Continuous Integration (CI) | |||||
Code Testing and Coverage | |||||
Performance Testing | |||||
Usability Testing | |||||
Accessibility Testing | |||||
Merge Trains | |||||
Review Apps |
Package |
Stage Lifecycle: Majority of users don’t work at GitLab Inc. (typically year 3) |
||||
Category | Today | Q3 | Q4 | Q1 | Q2 |
Date | by 2021-10-31 | by 2022-01-31 | by 2022-04-30 | by 2022-07-31 | |
Package Registry | |||||
Container Registry | |||||
Helm Chart Registry | |||||
Dependency Proxy | |||||
Dependency Firewall | |||||
Git LFS |
Secure |
Stage Lifecycle: Majority of users don’t work at GitLab Inc. (typically year 3) |
||||
Category | Today | Q3 | Q4 | Q1 | Q2 |
Date | by 2021-10-31 | by 2022-01-31 | by 2022-04-30 | by 2022-07-31 | |
SAST | |||||
Secret Detection | |||||
Code Quality | |||||
DAST | |||||
Fuzz Testing | |||||
Dependency Scanning | |||||
License Compliance | |||||
Vulnerability Management |
Release |
Stage Lifecycle: Usable for most GitLab users (typically year 4) |
||||
Category | Today | Q3 | Q4 | Q1 | Q2 |
Date | by 2021-10-31 | by 2022-01-31 | by 2022-04-30 | by 2022-07-31 | |
Continuous Delivery | |||||
Pages | |||||
Advanced Deployments | |||||
Feature Flags | |||||
Release Evidence | |||||
Release Orchestration | |||||
Environment Management |
Configure |
Stage Lifecycle: Majority of users don’t work at GitLab Inc. (typically year 3) |
||||
Category | Today | Q3 | Q4 | Q1 | Q2 |
Date | by 2021-10-31 | by 2022-01-31 | by 2022-04-30 | by 2022-07-31 | |
Auto DevOps | |||||
Kubernetes Management | |||||
Delivery Management | |||||
Secrets Management | |||||
ChatOps | |||||
Serverless | |||||
Infrastructure as Code | |||||
Cluster Cost Management |
Monitor |
Stage Lifecycle: Not used at GitLab Inc. (typically year 1) |
||||
Category | Today | Q3 | Q4 | Q1 | Q2 |
Date | by 2021-10-31 | by 2022-01-31 | by 2022-04-30 | by 2022-07-31 | |
Runbooks | |||||
Metrics | |||||
Incident Management | |||||
On-call Schedule Management | |||||
Logging | |||||
Tracing | |||||
Error Tracking | |||||
Product Analytics |
Protect |
Stage Lifecycle: Not used at GitLab Inc. (typically year 1) |
||||
Category | Today | Q3 | Q4 | Q1 | Q2 |
Date | by 2021-10-31 | by 2022-01-31 | by 2022-04-30 | by 2022-07-31 | |
Container Scanning | |||||
Security Orchestration | |||||
Container Host Security | |||||
Container Network Security |
Enablement |
Stage Lifecycle: Users of other tools start to switch (typically year 5) |
||||
Category | Today | Q3 | Q4 | Q1 | Q2 |
Date | by 2021-10-31 | by 2022-01-31 | by 2022-04-30 | by 2022-07-31 | |
Global Search | |||||
Code Search | |||||
Omnibus Package | |||||
Cloud Native Installation | |||||
Geo-replication | |||||
Disaster Recovery |
Learn how to make changes to categories and their maturity on our website handbook page.