Announcing Gitorious 3.1

We’re happy to announce Gitorious 3.1 – a minor upgrade bringing several new features, many improvements and lots of bugfixes.

Detailed list of the changes can be found in our CHANGELOG, the highlights of this release are presented below.

New features and notable changes

Our commenting system got further improvements. On all diff views you can now open multiple inline comment forms, meaning you can write and preview the comments independently. Also, you won’t see any unnecessary page reloads when commenting on either commits, diffs or merge requests anymore. It’s worth to mention that displaying of the comments is now driven by React.js, which had proven to be a great fit for this use case.

Teams page now lists the teams in alphabetical order, project page lists the repositories in alphabetical order too. It makes finding teams or repositories much easier.

If you’re an admin in your company and you want to manage SSH keys used by your users to push then we have something for you. We added a new page to the admin panel (accessible at /admin path), which is a simple interface for adding and removing SSH keys of all the users in Gitorious.

Another new thing on the administration side is the ability to use external SMTP server for sending all Gitorious emails by creating config/smtp.yml file. See config/smtp.sample.yml for details.

One of the requested features was ability to automatically grant access to all of the repositories for all of the users in Gitorious installation. We’re happy to introduce this feature in the form of the “super group”. Super group is a special system group that contains all of the users, and it’s added to all of the projects, both existing and new ones. To enable it make sure you have enable_super_group: true in gitorious.yml config file.

To ease troubleshooting we have included more information in application’s log file (production.log). Now every logged request additionally includes timestamp, pid of the worker process and UUID identifier.

One thing that got lost in our previous release was the user’s ability to change its website/blog URL (which is displayed on his/her profile). It’s back and you can find it on your user settings page.

Last but not least, we made lots of cleanup and internal refactoring of the code making it easier for us to work with and easier for the community to contribute.

Stability improvements

This release brings lots of bugfixes related to the overall stability and security of Gitorious.

In this version Gitorious was upgraded to run on Ruby on Rails 3.2.19, the latest stable and secure version of Rails in 3.x series, which fixes many security issues found in recent months. Ruby version was upgraded from 1.9.3 to 2.0, giving noticeable performance boost to the application, making it feel snappier.

We fixed several XSS vulnerabilities, Wiki and README files rendering, and crashing of background job processors. Merge requests were improved too. Caching of merge request diffs has been fixed, merge request creation page now properly handles diverged branches, and the numbering of newly created merge requests has been made predictable and consistent.

That’s not all when it comes to fixes and improvements. You can read the comprehensive list in the CHANGELOG file.

Installing or upgrading

To install Gitorious 3.1 on your server please refer to the Community Edition installation instructions. If you’re interested in supported Gitorious Enterprise Edition get in touch via If you’re already a Gitorious customer we’ll discuss the upgrade with you soon.

To upgrade your existing Community Edition installation to 3.1 please refer to the Upgrading guide.

%d bloggers like this: