Gitlab 2.0

December 22, we released version 2.0.

Major changes:

• Moving from gitosis to gitolite.
• Revised design. Now it is more convenient and practical.
• Improved Rights Management
• Improved email system - notifications.
• Improved dashboard.
• Improving the work of the file tree and directories.
• Atom tape for komitov and Taskov.
• Bagofix + other minor changes.

Future plans:

• Refactoring
• Performance optimization
• comments on the line of code.
• lightweight pushes (pivotal like)
• Extended access control per brunch.
• Work with hukami. Email notification during push operation
• Automatically creating brunches and deleting them when creating a merge request or issue (as an example). There is no clear idea how it will work.
• JSON API
• usability network graph
• Works towards integration with the services of continuous integration
• LDAP authorization
• WIKI

')
I want to tell you more about our innovation Merge request. This is a lightweight replacement githabby fork. The forks model fits very well on opensource development. But since our project has a different goal, the principle is slightly different.
Merge Request is a request for merge from one branch to another. For example, I created a feature_feed brunch and made 5 commites into it. With the help of the merge request, he indicated his desire to do a merge at a dev brunch. Now a person who has the right to push to dev can look at diff (for all 5 committees in total) and make an appropriate decision, as well as write a comment. While the rights to push are of a formal nature, however, it will soon be possible to control access to the branches. There will also be added the ability to carmaker and automatic removal of brunch if desired.

UPD: Link to the project