GitLab is an integrated product for the entire software development lifecycle. With each monthly release, we work to bring more aspects of social coding, continuous integration, release automation, and monitoring into a single tool. With GitLab 9.3, we're helping teams improve code quality, reduce cycle time and make complex projects easier to manage.
If your new features often get stalled in the initial discussion phase, read our four tips for shortening the conversation cycle and shipping faster.
In spirit of the rapidly approaching summer-vacation season, here are some tips on how to prevent burnout when scheduling on-call rotations. Although I'm currently a developer advocate, I've been a career developer and worked in DevOps roles, and I'm no stranger to the on-call life. Here I'll discuss burnout, the pros and cons of different shift lengths, and how to make on-call rotations a little less painful.
Today we are releasing versions 9.2.5, 9.1.7, and 9.0.10 for GitLab Community Edition (CE) and Enterprise Edition (EE).
Note: Please see the warnings in the Upgrade barometer section before upgrading.
Note: Versions 9.2.3-9.2.4, 9.1.5-9.1.6, and 9.0.8-9.0.9 contain incomplete fixes for the reserved namespaces / group renaming issue
These versions contain several security fixes, including a fix for a difficult to exploit persistent Cross-Site Scripting (XSS) vulnerability, improvements to API protections when using session authentication, fixes for several information disclosure vulnerabilities, and a fix for a flaw that could allow the deletion of project avatars. We recommend that all GitLab installations be upgraded to one of these versions.
Please read on for more details.
It's always been a goal for the Ticketmaster mobile team to get to weekly releases. In the first half of this year we were able to accomplish it, delivering new versions of both the Android and iOS app on a weekly basis since February. We've seen the positive impact on our fans, and it was even easier than we thought – making our entire application development process that much better.
But it didn't start out this way…
Release early and often, respond quickly to customer feedback, iterate. Rinse, repeat. The value of getting new features and products in front of customers faster has made its mark on the business world. As a result, development teams are under pressure to shorten release cycles and meet tighter deadlines all while maintaining high quality and security standards. How do experienced teams do it?