GitLab is open source software to collaborate on code. Today we announce the release of a new version of GitLab Community Edition (CE) and GitLab Enterprise Edition (EE), with new features, usability and performance improvements, and bug fixes. With this release we introduce Group Milestones. Group Milestones allow you to see a grouped list of milestones from all projects in a group. This makes working with multiple projects much easier. Also new are @all mentions in comments and improved code highlighting. In addition to the updates from Community Edition, GitLab Enterprise Edition received various bug fixes.
This release's most valuable person (MVP) is Jeroen van Baarsen for his work as a merge marshal on the issue trackers, thanks Jeroen!
This feature allows you to see all milestones in a group, grouped by title. This makes it much easier to release software when working with multiple projects.
The milestone page shows you all issues from all projects that have the same milestone name.
If your repository has VERSION file - it will be rendered on the project sidebar. For instance, if you need to check the version of a library, this can save you some time.
In GitLab Enterprise Edition we've previously changed the sign in page to implement customization. In order to reduce the difference between CE and EE we've ported the new look to CE.
We've put some effort into improving discussion. Now, outdated comments will be hidden under the cut. If you still want to see these, you can easily expand the outdated comments.
It is possible to configure GitLab Enterprise Edition so that users have their SSH public keys synchronised with an attribute that contains their key in their LDAP object. Existing SSH public keys that are manually managed in GitLab are not affected by this feature. To enable LDAP SSH key synchronization you need to tell GitLab which LDAP attribute holds the SSH keys.
A group on the LDAP server can be given GitLab administrator access. This ensures that the list of administrators in GitLab is always up to date. The LDAP Common Name of the group that holds your administrators needs to be configured on your GitLab server.
If you are setting up a new GitLab installation please see the installing GitLab page.
Upgrade instructions for omnibus-gitlab packages can be found in the omnibus-gitlab repository.
If you still want to do it manually - see the Update Guide.
For LDAP group support and more have a look at the feature list of GitLab Enterprise Edition.
Access to GitLab Enterprise Edition is included with a subscription.