So, you want to plan a product release? Well, let’s be honest, no one really wants to plan a product release; it’s a complex and exhausting process that requires the buy-in of various people across your organization.

An SCM such as Git is more than just a database for source code. It’s not only the thing you need to interact with to get code to production, but also a log of changes on a project. It’s not just the last couple of weeks of commits that are worth looking at. Any commit remains relevant weeks, months and years later. A commit serves multiple purposes. The first one is to explain a change during its review and the second is to explain a change to a future reader.

We’ve always been focused on creating tools that make development teams more productive. In 2014, we introduced GitKraken, the legendary cross-platform Git GUI: an intuitive tool to visualize what’s going on under the hood of Git in a way that makes version control less intimidating for individual developers and more scalable for organizations. Next came Glo Boards, a Kanban tool for project managers and developers.

Introduction One of the SRE team’s goals at Moogsoft is to make sure our feature teams have an easy path from local code changes to production. Changes rolling out to production mean new features, bug fixes, optimizations, and more, which translates into value added for our customers. In short, at Moogsoft we are all about making sure our product is continually evolving, and one way the SRE group helps is by building shared Jenkins functionality our engineers understand and can use quickly.

In today’s ever-changing world of DevOps, it is essential to follow best practices. That goes for security, access control, resource limits, etc. One of the most important things in the world of DevOps is continuous integration and continuous delivery, or CI/CD. Continuous integration is a crucial part of an efficient deployment. We are all guilty of repeating manual steps over and over again – especially when it comes to node configuration.

Two years ago, on June 4th of 2018, Microsoft announced its acquisition of GitHub, unicorn darling of the developer tools startup ecosystem, for $7.5B in stock. The announcement unearthed a wide range of opinions and pontifications, ranging from “GitHub is doomed” to “Microsoft is smart”, with many predictions about GitHub’s future. Some thought Microsoft’s growing investments in its cloud offering, Azure, might help GitHub.

Project management and issue tracking are foundational to a successful development team. Furthermore, task tracking tools that enable automation help maximize productivity, organization, and collaboration. We called in some help from Hogwarts on this release to introduce some truly magical features to GitKraken Boards. We bring you: Column Automation.

This week, Canonical announced the integration of Charmed Kubernetes with Microsoft Azure Arc. This integration provides businesses with a centralised place to manage their Kubernetes clusters and deploy their applications at scale, from cloud to the edge. The Azure Arc dashboard enables management and governance of any Kubernetes, across any substrate.