The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
GitLab helps teams accelerate software delivery and reduce cycle times, by improving efficiency and collaboration. Essential to software delivery, is the process of creating each improvement. The Create stage delights engineers, designers, and product managers with tools to design, develop, and review these improvements efficiently.
How users easily discover and configure product features.
源代码管理可以帮助整个软件开发团队充分协商、共享和协作，极狐GitLab可以帮助组织团队快速协作并迭代新功能，交付业务价值。 This category is at the "lovable" level of maturity.
Review code, discuss changes, share knowledge, and identify defects in code among distributed teams via asynchronous review and commenting. Automate, track and report code reviews. This category is at the "lovable" level of maturity.
Share documentation and organization information with a built in wiki. This category is at the "viable" level of maturity.
Focused on building an amazing experience for editing and building static sites. This category is at the "viable" level of maturity.
Focused on improving the GitLab Handbook.
Improve and maintain the features, style, and build process for the GitLab Documentation website.
A full featured Integrated Development Environment (IDE) built into GitLab so you can start contributing on day one with no need to spend days getting all the right packages installed into your local dev environment. This category is at the "viable" level of maturity.
Tools that support developers where they work and how they work with GitLab.
Store and share bits of code and text with other users. This category is at the "complete" level of maturity.
Gitaly is a Git RPC service for handling all the git calls made by GitLab. This category is planned, but not yet available.
Integrations are places where the GitLab product connects to features and services from other products. These integrations seek to offer our customers a seamless experience between these products, and range from lightweight features like Slack notifications for projects, to deep and complex integrations with Atlassian JIRA that connect a wide array of functionality throughout the GitLab product.
The GitLab API enables other products and services the ability to integrate with the GitLab product.
GitLab Development Kit (GDK) provides a collection of scripts and other resources to install and manage a GitLab installation for development purposes.
Allow users to import from Jira without losing required data
Primary Personas Served:
Growth driver: Initial purchase
Fault tolerant Git storage using Gitaly Cluster reduces the likelihood of outages or performance degradations, so that developers remain productive and deployments can always occur.
In FY22 we will build on the foundations laid in FY21 with Gitaly Cluster, to improve the ease of management and performance of Gitaly Cluster. We will achieve this goal by deploying Gitaly Cluster to all of GitLab.com to improve its performance and availability, and harden Gitaly Cluster under extreme production loads. This is not without challenges, particularly managing storage costs at petabyte scale.
It is also important that Gitaly Cluster is deployed to GitLab.com in full, so that the performance and fault tolerance benefits it offers are not exclusively benefits of a self-managed GitLab instance.
Growth driver: Expansion
Binary files are common in many software development projects, from video games to machine learning. It is common to side-load these files through pointer-based approach like Git LFS, but this kind of solution creates significant complexity for everyone who contributes to the project. Git's Partial Clone feature provides many of the fundamental features needed to be a compelling alternative to Git LFS and a pathway to Git from Perforce for binary workflows.
In FY22, we will make these workflows viable for video games and machine learning applications.
Further improvements are still needed for:
Key improvements planned include:
Growth driver: Retention
Code review is an essential best practice of every successful software project. It is necessary for maintaining the quality of code and products. GitLab's powerful and comprehensive code review capabilities make this possible, but have a steep learning curve, and can feel cumbersome and complex.
In FY22, we must make the core code review workflows fast (performance) and delightful (usability) for:
In order to be successful, we will also need to work with Ops and Sec so that testing, quality and security are native to code review. It is important that our solutions do not simply reflect GitLab's organizational structure, but instead solves problems for the people who use GitLab. Success will help developers be more productive, and improve cross-stage adoption.
Key improvements planned include:
Growth driver: Retention
Open source projects not only allow us to use powerful and sophisticated tools, it also provides the opportunity to find and connect with different communities, take on new challenges, and most importantly, provide valuable contributions back to the community.
Many of the same obstacles faced across large OSS projects are also found in large organizations, where collaboration across teams is beset with workflow, security, and access problems.
We want to make GitLab the reference tool to contribute to open source projects and at the same time enable large organizations to set standards and best practices with minimal effort. Complex workflows that enable this collaborations should work out of the box with sane defaults in project setup/configuration.
In FY22 we will build on the solid foundations which allow users to contribute to projects today, namely by improving our forking workflows and by making contributing across GitLab instances fast and easy.
Key improvements planned include:
Growth Driver: Expansion
In 2021, our focus for our editors will be on setting up the right architectures for long term success and unifying editing in several places inside the application. Features that are added in one place, such as the static site editor, should also propagate into other editing experiences, such as the issue/MR description and wikis.
Growth Driver: Initial Purchase
While GitLab is a complete DevOps platform delivered as a single application, we realize that many other tools are used to aid in the product development process and that in certain situations, these tools cannot be replaced. In early 2020, the Ecosystem team moved into the Dev section and is focused on "mass integration" at the Instance and Group level in addition to better integration with popular tools on the market such as Jira, Confluence, Slack, ServiceNow, and Datadog.
Increasing efficiency, and reducing cycle time is an important way that GitLab provides value to customers. Reducing the cycle time from first commit until a change is merged is a way that we can determine if the improvements being made to the Create stage are contributing to this goal.
There are several large competitors, and many smaller competitors in specific categories. The large competitors are:
Detailed competitive landscapes are available in each category direction.
These JTBD relate to the Code Review category of the Source Code group. The statements were drafted for the FY21-Q2 Category Maturity Scorecard and have not been validated yet.
|When product improvements are identified, I want to propose changes that address them, so that I can help build a better product.||Issue|
|When my teammates propose changes, I want to review them before they are accepted, so that I can help increase the quality of changes, minimize the risk of defects, minimize the risk of out-of-scope changes, and grow the team’s expertise.||Issue|
The Create stage pricing strategy balances the needs of individual contributors, with the needs of enterprises, to create a cycle where individual contributors gladly and rapidly adopt GitLab, and naturally create the business case for upgrading to a suitable tier, typically Premium and above. The core pillar of the Create stage is the merge request based development workflow. This touches Source Code Management, Code Review, Gitaly and the Web IDE, and is heavily influenced by individual developers, and managers who implement access controls for efficiency, quality and compliance purposes. Our investment and pricing philosophy is to:
The tier for individual contributors, personal projects, or small teams trialing GitLab, Free is important for expanding (measured by GMAU and SMAU) the number of contributors in GitLab to include designers (Design Management), and marketers (Static Site Editor), and retaining our core users Developers (SCM, Code Review, Web IDE). Expanding support for different markets and use cases through improved binary file and monolithic repository workflows begins at the individual contributor level, as does supporting new personas like designers and marketers.
The tier for teams, Premium is enterprise ready and delivers important access controls and workflow controls needed for multiple teams to collaborate on the same large project. The Premium tier features for Source Code Management, Code Review and Gitaly are already mature, and very valuable to medium and large enterprises. Many feature requests and improvements driven by Premium customers are improvements to the experience of individual developers, which facilitates growth through expansion and standardization on GitLab.
The tier for Executive buyers with strategic objects for their business, this tier is primarily supported through Audit and Compliance capabilities that extend project level access control features.
At present there are no Ultimate features planned for implementation by groups in the Create stage. This is due to support from the Manage stage, and demand from new and existing customers being focused on the individual developer experience, or access controls that meet the Premium tier definition.