Mattermost Beta1 now available

We’re happy to announce Mattermost Beta1 (v0.7.0) is now available for download. Detailed changes can be found in our release notes. Please share questions and feedback on the Mattermost forum, which is monitored regularly by the Mattermost core team.

The focus of Beta1 was on GitLab Mattermost–a co-branded version of Mattermost integrated with GitLab security that now ships as part of the GitLab omnibus installer.

GitLab is the world’s leading on-prem software collaboration platform–used by over 100,000 organizations–and we were thrilled by their GitLab loves Mattermost blog post announcing their adoption.

Less than three weeks later, we’re extremely pleased that our Beta1 release incorporates much of the feedback from GitLab Mattermost users, specifically:

• Integrated Security – GitLab users wanted an option to run GitLab Mattermost entirely off GitLab security, so provisioning in organizations could be centrally managed via Active Directory/LDAP. This is now supported in Beta1 via GitLab SSO.

Mattermost Beta1 now offers an option to run GitLab Mattermost entirely off GitLab security so provisioning can be centrally managed via Active Directory/LDAP.

• Migration Support – These requests came in two parts, first was the ability to import Slack user accounts and message histories (Beta1 ships a preview of this feature), and the second was for tools and processes to upgrade and migrate Mattermost deployments (which is now scheduled for Mattermost Beta2 shipping October 2, 2015).

Example of Mattermost import from Slack

• Transparency – Repeatedly we had questions from GitLab users about Mattermost release dates, feature roadmaps, and product direction. A significant part of Beta1 was adopting good habits from the GitLab community and making Mattermost release schedule public, publicly posting our feature roadmaps and writing down the Mattermost product vision.  We’re also picking up the habit of incrementally updating our changelog and release notes so it’s easy to see what’s coming in the next release.

Mattermost Product Roadmap

In addition to these priorities, we fixed an assortment of smaller issues, such as restricting team creation to email accounts from a specific list of domains, and switching to an MIT License for the compiled version of GitLab Mattermost to align with GitLab licensing.

We’re extremely happy to be engaged with the GitLab community (via GitLab Mattermost issue tracker, GitLab Omnibus issue tracker, GitLab Mattermost category in the Mattermost forum, Twitter, Google Hangouts, GitLab Disqus forums, and the Mattermost issue tracker). Whatever way you’d like to reach us, we’re happy to hear from you.

Finally, we’d like to recognize the many people who’ve contributed to the success of Beta1:

Many thanks to our external contributors. In no particular order:

• asubset
• felixbuenemann
• CtrlZvi
• BastienDurel
• manusajith
• doosp
• zackify
• willstacey

Special thanks to influential members of the GitLab community who helped shape this release, and who play a pivotal role in bringing Mattermost to over 100,000 organizations using GitLab today. In no particular order:

• cifvts
• LongLiveCHIEF
• Chryb
• cookacounty
• bweston92
• mablae
• picharmer
• cmtonkinson
• cmthomps
• m.gamperl
• StanMarsh
• alx1
• jeanmarc-leroux
• dnoe
• dblessing
• mechanicjay
• larsemil
• vga
• stanhu
• kohenkatz
• RavenB1
• booksprint
• scottcorscadden
• sskmani
• gosure
• jigarshah

Extra special thanks to GitLab community leaders for making the release of GitLab Mattermost such a success:

• marin
• sytse