This page describes the direction and roadmap for GitLab. It is organized from the short to the long term.
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.
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.
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.
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.
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.
No current issues
dependenciesto .gitlab-ci.yml (EE-only?)
No current issues
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:
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: