Don’t you just love getting last-minute feedback from your boss right before your deadline? What about combing through a deluge of irrelevant-but-weighty comments from coworkers who aren’t even working on your project?
Pryvit! Mattermost 5.6 is filled with new features designed to increase team productivity:
At Atlassian, we want to give our customers choice in how they deploy Atlassian products: in the cloud, managed by Atlassian, or on the infrastructure of your choice with Server or Data Center. Many of our on-premise customers begin their Atlassian journey with our server products, with the ability to download our software and install it on a single server that you control. This gets you up and running quickly.
Mattermost dot release 5.5.1 for Team Edition (TE) and Enterprise Edition (EE) is now available for download. If your deployment is affected by issues this dot release fixes, upgrading is recommended. Otherwise, you can upgrade to the next monthly release which also includes these fixes.
Picture boring a new subway tunnel while the city above you goes on about its business, oblivious to the machinations under the surface. That’s pretty much the project we completed earlier this year. Only we were working in the cloud.
Once a year, PagerDuty’s SREs get together for a three-day, in-person offsite. With the team spread across three time zones in the U.S. and Canada, encompassing two offices and three remote members, face time is rare and valuable. We use our offsites for thoughtful discussions on team health, long-term project roadmap planning, refining and updating our team’s mission, and to simply spend time together as a team.
Just when you think you’ve got this whole “knowledge economy” thing figured out, here comes the “creative economy” – the world in which your ability to succeed and add value is limited only by your imagination. Of course, that creativity needs to be informed by a deep understanding of your customers.
Major incidents are inevitable, and fixing them is the top priority for any ops or DevOps team. But what happens after service is restored? Do teams take the time to fully understand what went wrong, then follow up to prevent it happening again?
