Mattermost v7.1 is now available
Mattermost v7.1 (Extended Support Release) is generally available today. The following new features are included (see changelog for more details).
Mattermost v7.1 (Extended Support Release) is generally available today. The following new features are included (see changelog for more details).
When the first supporting server-side infrastructure for Collapsed Reply Threads (CRT) shipped with Mattermost v5.29 (November 2020), it included an ominous release note: > This setting is enabled by default and may affect server performance. While performance concerns are possible with any new feature, most features don’t require significant architecture and data model changes. Most features don’t ship incrementally across 20 monthly releases. And most features – to their credit?
Get ready for the future of Mattermost mobile. Beta testers can now access Mobile v2.0, including multi-server support — our most requested mobile feature ever. We’re also bringing you a number of usability enhancements and performance improvements to make you productive on the go. If you want to be on the cutting-edge of Mattermost mobile development, we’d encourage you to join the mobile beta program today.
Morph is a new database migration tool designed to improve Mattermost schema migrations. It can be used programmatically with a library and from a CLI. Morph stores the schema version in a table, where all applied migrations are persisted. It’s a flexible open source library that can be used with a driver interface implementation and a source to read migration scripts from. The engine uses a dependency injection pattern so that any implementation can be used with the library.
Mattermost v7.0 is generally available today and includes three of our top five most requested features, based directly on your input in our feature idea forum. The following new features are all included (see changelog for more details).
Building software is hard. Building cloud software is even harder because things move much faster — and require mission-critical reliability and availability. To effectively build software in the cloud, engineering teams need observability, CI/CD, reporting, and lots of tooling. At every organization I’ve worked at, we’ve needed a system of tools that lets us: But all the tools available to engineering teams never quite fit together with our specific processes.
For teams that follow a structured build and release cycle, having a reliable, shared workflow makes the difference between chaos and consistency. With every new feature in development the team needs to know what the specs are, how it fits in the roadmap, what the customer feedback was, where to find the repository, who is responsible for each step, and so much more.
Releasing software to users has become a sophisticated and intricate process that requires high levels of consistency and coordination. A release has to be built, brought together, documented, tested and deployed, which requires coordination of at least four separate teams and a generous handful of pipelines and other tools. Without a well-documented process things can get messy very quickly, causing stress for everyone involved.
Whether you’re part of a team managing SaaS products or a high-security digital workspace, sometimes Things Go Wrong and must be addressed with extreme care, professionalism, and predictability. For outages, data breaches, vulnerabilities and more, you and your team are juggling a variety of tools, processes, and rigid incident management systems. When the on-call pager goes off at 3 am almost no one has the ability to remember every step needed to kick off all the response workflows.
The Apps Framework is an important tool in the Mattermost developer toolbox for easily creating integrations and customized workflows—written in any language and deployed with serverless hosting. The Apps Framework complements the existing ecosystem of plugins, slash commands, bots, and webhooks. As of Mattermost version 6.6, the Apps Framework is now generally available for all cloud and self-hosted deployments.