GitLab can be compared to the more familiar GitHub but contains a number subtle differences . It is an environment for managing Git repositories on-premises . It is issued under the MIT Expat license and developed in Ruby on Rails. It is available in two versions, namely the free to use Community Edition and a paid Enterprise Edition, with more features aimed at large companies. The two flavors are explained on this page . The development team has released GitLab 11.3 and the release notes for this release can be found below.
GitLab 11.3 released with Maven Repository and Protected Environments
With our shipment today of GitLab 11.3, we are excited to announce support for Maven repositories, Code Owners, Protected Environments, and epic forecasting. These features help automate controls around environments and code while providing further efficiencies for Java developers.
We have expanded our support for Java projects and developers by building Maven repositories directly into GitLab. This provides Java developers with a secure, standardized way to share version control in Maven libraries and save time by reusing these libraries across projects. This feature is available with GitLab Premium.
Code Owners and Protected Environments
GitLab Starter now supports the assignment of Code Responsible for the code. This feature prepares us for futures releases that will enforce internal controls at the code level.
Available in GitLab Premium, operators can also use Protected Environments to set permissions. This is a new portfolio management feature in GitLab Ultimate can automatically forecast an epic start and end dates based on the milestone dates of its issues. With this enhancement, portfolio managers will be able to compare their planned start and end dates to the work that is scheduled through milestones, gaining visibility into potential slippage in epic delivery. This will enable faster, better decisions on what can be arranged and adjusted.