<story><title>GitLab 4.0 Released</title><url>http://blog.gitlabhq.com/gitlab-4-release/</url></story><parent_chain></parent_chain><comment><author>BUGHUNTER</author><text>From the website:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  What we removed in 4.0: 
  SQLite support (I like it but this database got locked
  when several users use gitlab at once)
&lt;/code&gt;&lt;/pre&gt;
This is a pitty! I am sure there are many small teams where sqlite is totally sufficient.&lt;p&gt;Have you been able to measure and determine the problems with sqlite more precisely? It would be interesting to see at which point (number of concurrent users) the problems occur. Also it just reads like some data accessing backend is not properly closing connection / file access, so blocking might be just a bug, not a sqlite limitation.&lt;p&gt;Did you read &lt;a href=&quot;http://www.sqlite.org/lockingv3.html&quot; rel=&quot;nofollow&quot;&gt;http://www.sqlite.org/lockingv3.html&lt;/a&gt; ?&lt;p&gt;I personally do like having such important infrastructure like bugtrackers as simple as possible, beeing able to setup anytime anywhere with sqlite backend is really a plus in changing environments.</text></comment>
<story><title>GitLab 4.0 Released</title><url>http://blog.gitlabhq.com/gitlab-4-release/</url></story><parent_chain></parent_chain><comment><author>n0nick</author><text>GitLab looks awesome, both features and design wise, but the installation process is so tedious and complicated that I quit in the middle of it more than once:
&lt;a href=&quot;https://github.com/gitlabhq/gitlabhq/blob/4-0-stable/doc/install/installation.md&quot; rel=&quot;nofollow&quot;&gt;https://github.com/gitlabhq/gitlabhq/blob/4-0-stable/doc/ins...&lt;/a&gt;&lt;p&gt;This is feedback I heard from fellow developers as well.&lt;p&gt;I&apos;m curious as to whether the maintainers are planning to simplify the list of dependencies and installation steps in the upcoming versions.</text></comment>