At GitLab we ship continuously. When code is written, it is reviewed, merged, and deployed to GitLab.com. This is a continuous train which runs on time - we've never missed a release which is every month. What's running on GitLab.com SaaS is packaged and released for GitLab Self Managed. We also publish a release blogpost to coincide with the monthly release.
Given this continuous integration/continuous deployment, code is constantly released and includes finished or in-flight features which could be in various states of visibility, behind feature flags, pre/post-beta, or generally available. This is really good for our speed of innovation, but we also want to have appealing narratives that we can share with our users to show them the value that GitLab, the DevSecOps platform, provides via Product and Product Marketing communication.
The changelogs for (GitLab Community Edition, GitLab Enterprise Edition, GitLab Runner) contains the log of entries for any given GitLab release, and the release posts contain details about some of the features within a given release, but these are not marketing vehicles.
Once per quarter we will select three features to explicitly launch and highlight in a blogpost, and where appropriate in other marketing content. Unlike individual release posts this content will be intentional about communicating:
We will not hold back features from prior releases, or release posts. Users may discover these features via our CHANGELOG or a release post item in the monthly blogpost. This is OK since our Launch will reach a broader audience than our release post.
This allows for Product/Product Marketing to tell a story about the launch of these features, highlighting them, and going into more depth than we do in the release post. This announcement includes the major and minor versions of GitLab including these features and goes into more depth about the value to the customer, why the feature got created, who asked for it, who contributed to it, as well as the Product Manager who led the feature, and discuss the progress made over time on it. We will also tie the feature to key Product Investment themes throughout the year highlighting how we continue to plan ambitiously and deliver results for our users.
The goal of these quarterly feature launches is not to slow down development or to hide things. We're open core and the source code is visible. By having quarterly feature launches, we're able to better highlight features in depth for our users, so they are less likely to overlook key feature additions.
Below are some high level details of how the GitLab Quarterly Launch Process works. (WIP)
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
Cookie Policy
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, enabling you to securely log into the site, filling in forms, or using the customer checkout. GitLab processes any personal data collected through these cookies on the basis of our legitimate interest.
These cookies enable helpful but non-essential website functions that improve your website experience. By recognizing you when you return to our website, they may, for example, allow us to personalize our content for you or remember your preferences. If you do not allow these cookies then some or all of these services may not function properly. GitLab processes any personal data collected through these cookies on the basis of your consent
These cookies allow us and our third-party service providers to recognize and count the number of visitors on our websites and to see how visitors move around our websites when they are using it. This helps us improve our products and ensures that users can easily find what they need on our websites. These cookies usually generate aggregate statistics that are not associated with an individual. To the extent any personal data is collected through these cookies, GitLab processes that data on the basis of your consent.
These cookies enable different advertising related functions. They may allow us to record information about your visit to our websites, such as pages visited, links followed, and videos viewed so we can make our websites and the advertising displayed on it more relevant to your interests. They may be set through our website by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant advertisements on other websites. GitLab processes any personal data collected through these cookies on the basis of your consent.