GitLab Direction

This page describes the direction and roadmap for GitLab. It is organized from the short to the long term.

Your contributions

GitLab's direction is determined by the code that is sent by our contributors. We continually merge code to be released in the next version. Contributing is the best way to get a feature you want included. On our issue tracker for CE and EE, many requests are made for features and changes to GitLab. The ones with the status accepting merge requests are pre-approved. Of course before any code is merged it still has to meet the contribution acceptance criteria.

What our customers want

At GitLab the company we try to make what our users and we need (many of us are or used to be developers). If a customer requests a feature, it carries extra weight. Due to our short release cycle we can ship simple feature requests (for example an API extension) within one to two months.

Previous releases

On our release list page you can find an overview of the most important features of recent releases and a links to the release blog posts.

Next releases (automatically generated)

GitLab releases a new version every single month on the 22nd. Note that we often move things around, do things that are not listed and don't do things that are listed. This page is always in draft, some of the things on it might not ever be in GitLab. New Products are indicated with 'New Product' in the issue title, this is our best estimate of what will be new products, it is not definitive. Also the list below not include any contributions from outside GitLab the company. The bullets list the tentpole features; the most important features of upcoming releases. This is not an authoritative list of upcoming releases - it just reflects current milestones. The CE and EE to the right of the version number link to all planned issues for that version.

The milestone, as seen below, is the intended date that the listed features get shipped.

GitLab Community Edition

8.13

GitLab Enterprise Edition

8.13

9.0

Wishlist

Below are features we'd really like to see in GitLab. This list is not prioritized. We invite everyone to join the discussion by clicking the wishlist item that is of interest to you. Feel free to comment, vote up or down any issue or just follow the conversation. For GitLab sales, please add a link to the account in Salesforce.com that has expressed interest in a wishlist feature. We very much welcome contributions that implement any of these things.

Major Wins

Usability

Code Review

Issue tracker

Version Control for Everything

Performance

CI

Pages

Container Registry

No current issues

Moonshots

New Products

Meta issues

We use meta issues to collect similar feature proposals, so that we can prioritize and review easily.

Scope

Our vision is the need for an integrated set of tools for the software development lifecycle based on convention over configuration. To achieve this we plan to ship the following stack of tools in our Omnibus package:

  1. Idea (Chat) => Mattermost ships with GitLab
  2. Issue (Tracker) => GitLab Issues ships with GitLab
  3. Plan (Board) => GitLab Issue Board
  4. Code (IDE) => Koding integrates with GitLab
  5. Commit (Repo) => GitLab Repositories ships with GitLab
  6. Test (CI) => GitLab Continuous Integration, and Container Registry ship with GitLab. We would love to add support for CodeClimate and have an extended vision for CI and CD.
  7. Review (MR) => GitLab Merge Requests ships with GitLab
  8. Staging (CD) => GitLab Deploy already ship with GitLab and we plan to ship with Review Apps
  9. Production (Chatops) => We plan to ship with a Slack bot and Cog integration
  10. Feedback (Cycle Analytics) => We plan to ship with Cycle Analytics and Prometheus

Outside our scope

  1. PaaS although we do want to use GitLab Deploy to deploy to CloudFoundry, OpenStack, OpenShift, Kubernetes, Mesos DCOS, Docker Swarm, Atlas/Terraform, Nomad, Deis, Convox, Flynn, Tutum, GiantSwarm, Rancher
  2. Configuration management although we do want to upload cookbooks, manifests, playbooks, and modules for respectively Chef, Puppet, Ansible, and Salt.
  3. Distributed configuration stores Consul, Etcd, Zookeeper, Vault
  4. Container configuration agents ContainerPilot, Orchestrator-agent
  5. Log monitoring ELK stack, Graylog, Splunk
  6. Infrastructure monitoring CheckMK, Nagios, Sensu
  7. Error monitoring Sentry, Airbrake, Bugsnag
  8. Network Openflow, VMware NSX, Cisco ACI
  9. Incident notification Pagerduty, Pingdom
  10. Network security Nmap, rkhunter, Metasploit, Snort, OpenVAS, OSSEC

Vision

From development teams to marketing organizations, everyone needs to collaborate on digital content. Content should be open to suggestions by a wide number of potential contributors. Open contribution can be achieved by using a mergeable file format and distributed version control. The vision of GitLab is to allow everyone to collaborate on all digital content so people can cooperate effectively and achieve better results, faster.

Ideas flow though many stages before they are realized. An idea originates in a chat discussion, an issue is created, it is planned in a sprint, coded in an IDE, committed to version control, tested by CI, code reviewed, deployed, checked and documented. Stitching all these stages of the software developement lifecycle together can be done in many different ways. You can have a marketplace of proprietary apps from different suppliers or use a suite of products developed in isolation. We believe that an integrated set of tools for the software development lifecycle based on convention over configuration offers a superior user experience. The advantage can be quoted from the Wikipedia page for convention over configuration: "decrease the number of decisions that developers need to make, gaining simplicity, and not necessarily losing flexibility". In GitLab you only have to specify unconventional aspects of your workflow. The happy path is frictionless from idea to production.

We admire other convention over configuration tools like Ruby on Rails (that doctrine of which perfectly describe the value of integrated systems), Ember, and Heroku, and strive to offer the same advantages for a continuous delivery of software.

We prefer to offer an integrated set of tools instead of a network of services or offering plugins for the following reasons:

  1. We think an integrated set of tools provides a better user experience that a modular approach, as detailed by this article from Stratechery.
  2. The open source nature of GitLab ensures that that we can combine great open source products.
  3. Everyone can contribute to create a feature set that is more complete than other tools. We'll focus on making all the parts work well together to create a better user experience.
  4. Because GitLab is open source the enhancements can become part of the codebase instead of being external. This ensures the automated tests for all functionality are continually run, ensuring that additions keep working work. This is contrast to externally maintained plugins that might not be updated.
  5. Having the enhancements as part of the codebase also ensures GitLab can continue to evolve with its additions instead of being bound to an API that is hard to change and that resists refactoring. Refactoring is essential to maintaining a codebase that is easy to contribute to.
  6. Many people use GitLab on-premises, for such situations it is much easier to install one tool than installing and integrating many tools.
  7. GitLab is used by many large organizations with complex purchasing processes, having to buy only one subscription simplifies their purchasing.