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.
We are proud to introduce the world to the most recent release of GitLens. We have added richer GitLab integration, Gerrit support, the ability to reorder your commits when making an interactive rebase, and more. We can’t wait for you to read all about what’s new in GitLens 12.1!
Welcome to the 9th edition of Open Source Matters: our regular publication about the latest happenings in open source! Let’s dive into the news.
Suppose you have to use your phone or other devices frequently, and you don’t want to type your password every time you wish to access an application. By implementing Trusted Device authentication, your system will recognize the device’s authentication and help you log in to the application quickly and safely. The whole process will not only save your time but will also allow you to witness an advanced authentication procedure.
Mattermost v6.7 is generally available today and includes the following new features (see changelog for more details).
Ask any engineer what they’d like to eliminate from their daily to-do list, and the answer will almost certainly be some version of reducing toil. Engineering organizations can burn hours and hours of work time on repetitive, manual tasks that reduce bandwidth for high-impact projects. That being the case, it’s no surprise that reducing toil helps your team work more productively and experience better job satisfaction in the long run.
Bringing the best software solutions to market as quickly as possible requires using automation to facilitate repetitive tasks (e.g., testing) so you can spend more time writing high-quality code. This is one of the main reasons why today’s top-performing dev teams build continuous integration (CI) and continuous delivery or continuous deployment (CD) pipelines, which enable them to ship new releases faster.
Most products that run as Software-as-a-Service (SaaS) are built to be multi-tenant, meaning that a single instance or deployment is meant to be used by multiple organizations. There’s a good reason for this: it’s generally easier to scale and operate multi-tenant applications. But in this new age of containers, orchestration, infrastructure-as-code, and Kubernetes, where it’s cheaper, faster, and simpler to deploy a new instance of an application, that may no longer be the case.
