GitLab 9.1 Released with Service Desk, Canary Deployments & more from GitLab

Read the latest news about GitLab and recent releases. [GitLab]( GitLab 9.1 Released with Service Desk, Canary Deployments, and Burndown Charts [Read more]( GitLab is designed to provide you actionable feedback in different stages of your application lifecycle, and on different timescales. With 9.1, GitLab introduces [Canary Deployments](. This allows you to deploy new code to a small portion of your fleet, providing you an opportunity to revert with minimal impact if something goes wrong. If a problem is detected, you can quickly revert, minimizing the impact on your users. This is immediate production feedback. As you expand your software products, GitLab's new [Service Desk]( feature in 9.1 enables your growing user base to send emails to your team via a dedicated address per project for any kind of feedback or support. These show up as GitLab confidential issues in your project. Commenting on them responds back to the original email sender, creating a brand new integrated user feedback channel right inside GitLab. GitLab 9.1 also introduces [Burndown Charts](, giving your team development feedback. As a team, you can now visualize and track the pace of issue completion throughout a milestone, giving you information to continuously make improvements in your processes over time. Announcing the new Community Writers Program [Get more information]( The GitLab Community Writers Program has changed. Now our community contributions will be published as Technical Articles in our Documentation Portal. You write, we publish, you earn up to USD 200 per article! The DevOps Journey: Using Containers with Red Hat Openshift and GitLab [Register now]( One of the major challenges of the transition to DevOps is managing the delivery of applications across multiple, potentially varied infrastructure and environments. For many teams, deployment of software still requires complicated installation and integration. However, adopting a container strategy can help. [Join us this Thursday for a live webcast with special guest Jason Dobies](, Principal Software Engineer at Red Hat, for a discussion on containers, the role they play in adopting and scaling DevOps workflows, and a live demonstration of how you can deploy from GitLab to a container using OpenShift. Demo - Mapping Work Versus Time, With Burndown Charts [Watch now]( Every software development team likely feels pressure to move faster, shipping more software in shorter time periods. With GitLab 9.1, we've introduced burndown charts to further help you track and manage your work. Burndown charts for projects help teams visualize the number of issues that are incomplete as they progress through a milestone. You can see the number of issues left to do, along with their cumulative issue weight, "burn down" over the remaining time before your deadline. This prepares teams to foresee obstacles and make decisions sooner, for instance on resources or scope, if risks emerge further along in their timeline. How Innersourcing Can Help Your Security Team [Read more]( Enterprise teams have a lot to gain from open source methods. Some of the most important of these include making all software projects visible by default to all employees, and allowing anyone who can see the code to fork it and make changes freely. New ideas can also arise by allowing people outside the project to suggest changes with pull and merge requests, and having a line-by-line conversation about the code. Using unit and integration tests lets developers make changes without fear of breaking things. Similarly, incorporating continuous integration ensures that every change is automatically tested. These principles can help the entire team collaborate, but they have some specific applications for the security team. [We're Hiring]( We're Hiring [Read Listings]( [Get In Touch]( Get In Touch [Contact Us]( [Contact Sales]( [about.gitlab.com]( [Login]( We want feedback on this newsletter! Please reply if you have requests or ideas for improvement. This email was sent to [{EMAIL}](. If you no longer wish to receive notifications please [unsubscribe]( here.