Gitlab is open source software made for collaborative coding. Today we announce the release of a new version of GitLab Community Edition (CE), with new features, usability improvements and bug fixes. The most notable new feature is the addition of public group profiles (see screenshot above).
This release's most valuable person (MVP) is Jason Hollingsworth for contributing the public group profile feature.
Markdown, wiki links and emoji
GitLab now renders newlines in Markdown text according to the specification, as previously discussed.
Relative links inside wiki pages stay inside the wiki, instead of pointing back to the accompanying repository.
Due to licensing reasons, GitLab 6.7 uses a new set of emoji based on the emoji gem and PhantomOpenEmoji. We thank Rei from Emojidex for creating freely licensed emoji's for GitLab.
In previous versions, a Git repository import could get stuck leaving the user no option but removing the repository from GitLab and recreating it. In GitLab 6.7, we have added an import timeout so that your import will not get stuck, and we have added a 'Retry' button in case the import failed due a transient condition.
Due to a rewrite of our Git access authorization system, Git over HTTP now requires that your GitLab server has at least 2 Unicorn workers (which is the default value). This means that small GitLab instances with only one Unicorn worker will only support SSH Git access going forward.
We advise users are running into the maximum HTTP push size of Nginx to update their configuration.
For a full list of changes see the CHANGELOG.
Contributing guide link on the 'New Issue' page
When a user creates a new issue in a repository containing a 'CONTRIBUTING' file, GitLab reminds them to read the contributing guide.
Merge Request diff view improvements
It is now possible to add commits to a branch in a Merge Request using the web editor: just click 'Edit' in the Merge Request diff view. In addition, you can now choose to hide diff comments.
New integrations: Gemnasium and Slack
If you are setting up a new GitLab installation see the installation section of the README.
If you have version 6.4.2 or higher you can use the upgrade script. But you have to update GitLab Shell to 1.9.1 manually, see point 3 of the upgrade guide.
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 GitLab.com subscription.
No time to upgrade or maintain Gitlab yourself? GitLab.com also offers upgrade and installation services as part of a GitLab.com subscription or alternatively on a consultancy basis.
We want to hear from you
Enjoyed reading this blog post or have questions or feedback? Share your thoughts by creating a new topic in the GitLab community forum.Share your feedback