Gitlab 2.0

    image
    On December 22, we released version 2.0.

    Major changes:
    • Moving from gitosis to gitolite.
    • Revised design. Now it is more convenient and practical.
    • Advanced Rights Management
    • Improved email notification system.
    • Improving dashboard.
    • Improving the operation of the file and directory tree.
    • Atom tape for commits and tasks.
    • Bagofiks + other minor changes.



    Future plans:
    • Refactoring
    • Performance optimization
    • comments on a line of code.
    • lightweight tasks (pivotal like)
    • Advanced access control for each brunch.
    • Work with hooks. Email notification for push operation
    • Automatic creation of brunches and their removal when creating a merge request or issue (as an example). There is no clear idea how it will work.
    • JSON API
    • usability network graph
    • Work towards integration with continuous integration services
    • LDAP authorization
    • Wiki


    I want to tell in more detail about our innovation Merge request. This is a lightweight replacement for the github fork. The fork model fits very well on opensource development. But since our project has a different goal, the principle is slightly different.
    Merge Request is a merge request from one brunch to another. For example, I created a feature_feed brunch and made 5 commits into it. With the help of merge request, I indicated my desire to merge into the brunch of dev. Now, a person who has the right to push in dev can look at diff (for all 5 commits in total) and make an appropriate decision, as well as write a comment. While the rights to push are formal, however, soon there will be an opportunity to control access to brunches. Also, the ability to automate and automatically remove the brunch if desired.

    UPD: Link to the project

    Also popular now: