February 2014 Summaries

GitLab is proposing a modification in how it renders line-breaks in markdown files to align with the markdown specification, which requires two or more spaces at the end of a line for a line-break to be rendered. This change aims to ensure markdown files appear consistent across projects, eliminating the current behavior where line-breaks are automatically rendered. Paragraphs will remain unaffected, continuing to be separated by one or more blank lines. This adjustment will apply universally across GitLab Flavored Markdown, affecting descriptions and comments in issues and merge requests. The goal is to maintain uniformity by avoiding different behaviors and rendering code for varied contexts, and GitLab is seeking feedback on this proposed change.

GitLab, an open-source application for managing git repositories, historically faced challenges with complex installation and update processes, which were cumbersome and lengthy. To simplify this, GitLab 6.4 introduced a single-command upgrade process, and further developments have streamlined installation with three new options: the GitLab Chef cookbook, GitLab Packer virtual machines, and GitLab Omnibus packages. The Chef cookbook offers flexibility for both development and production environments across multiple operating systems, supporting various databases and cloud services like AWS Opsworks. For quick server setups, Packer virtual machines come preinstalled with GitLab, while Omnibus packages, though initially limited in features, represent a significant step towards easier package management. These advancements aim to enhance GitLab's usability and scalability, backed by community collaboration to address ongoing improvements. Despite these new methods, previous installation options remain available, underscoring GitLab's commitment to accessibility and community support.

GitLab announced a change to the licensing of its Enterprise Edition (EE) to clarify that a valid subscription is required for its use, as the previous open-source license created confusion about subscription necessities. This change aims to reduce misunderstandings and encourage potential subscribers to choose GitLab as their primary code hosting tool. Since its introduction in 2013, both the Enterprise and Community Editions have grown, with the Community Edition's user base doubling to 50,000 organizations. Despite the licensing change for EE, GitLab emphasizes its commitment to the Community Edition by continuing its development and releasing new features and bug fixes, ensuring it remains a fully functional application without restrictions. Additionally, GitLab.com staff plan to contribute more features to GitLab Community Edition and GitLab CI in the future, maintaining the improvement trajectory of all GitLab versions.