Thanks for the feedback and for listing the features that you are concerned about.<p>The squash functionality is likely to stay EE only since it is similar to rebasing. Rebasing is EE only because larger enterprises are more likely to have this workflow.<p>Regarding the &#x27;test the merge&#x27; functionality I&#x27;ve only heard requests from large organizations for that, can you detail the context in which you want to use it?<p>The code analytics is a typical enterprise feature in my view.<p>I think that the private&#x2F;confidential issues in <a href="https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues&#x2F;3678" rel="nofollow">https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues&#x2F;3678</a> is something that are needed for really large organizations and for people hosting on GitLab.com, so in my view it can be EE only.<p>For all of the above I try to keep an open mind, so feel free to push back. Based on discussions here we do decide to merge features into CE, for example the branded homepage <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=10931690" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=10931690</a>