Why we're not leaving the cloud and more from GitLab

[GitLab]( Why we're not leaving the cloud [Read more]( Towards the end of 2016 we said we were leaving the cloud for bare metal and shared our hardware proposal. In December 2016, after receiving hundreds of comments and emails filled with advice and warnings, Sid and the team decided to keep GitLab.com in the cloud. The rest of the post summarizes some of the great community support and feedback we received and ends with how we are committed to making GitLab.com fast and stable in the cloud. Simplifying the Software Development Lifecycle [Register for the webcast]( Software has taken over the world and businesses across industries are expected to deliver excellent digital experiences. As the speed of change and demand in technology continues to accelerate, how does your organization stay flexible enough to respond quickly without sacrificing quality? In this webcast, Product Manager Régis Freyd shares: - The benefits of built-in project management best practices - Why integrated, automated, and accessible monitoring is a competitive advantage - What to expect from GitLab Enterprise Edition 9.0 and beyond [Join us]( this Friday, March 10, at 7 pm UTC (11 am PT) and learn techniques to eliminate error-prone processes from your workflow. Can't make it? Register anyway and we will send you the recording. Invite Your Engineers To Talk Business. Here's Why. [Read more]( Every business today is a technology business. Whether it supports your business model or itself is the business model, your technology stack plays a key role. What your engineering team ships, and how they ship, has direct and measurable consequences for your business, even if they traditionally prefer to think otherwise. Engineering goals are now closer than ever to business goals, and understanding that will help companies thrive in the business technology world today. We are changing the IP of GitLab Pages on GitLab.com [Learn more]( What is changing? We are changing the IP address of GitLab Pages server on GitLab.com to 52.167.214.135. Which websites will be affected? Only websites hosted with GitLab Pages on GitLab.com set up with a custom root domain, which have a DNS A record pointing to 104.208.235.32, will be affected. Which GitLab Pages websites will NOT be affected? No other websites hosted with GitLab Pages will be affected, more specifically: - On-premise GitLab will not be affected - GitLab Hosted (GitHost) will not be affected - GitLab.com websites with default Pages domains will not be affected - GitLab.com websites with custom subdomains set up with DNS CNAME records will not be affected [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.