{"id":16645,"date":"2020-05-22T08:19:43","date_gmt":"2020-05-22T08:19:43","guid":{"rendered":"https:\/\/www.mautic.org\/mautic-community-introduces-multiple-major-improvements\/"},"modified":"2025-06-19T11:55:08","modified_gmt":"2025-06-19T11:55:08","slug":"mautic-community-introduces-multiple-major-improvements","status":"publish","type":"post","link":"https:\/\/mautic.org\/blog\/mautic-community-introduces-multiple-major-improvements","title":{"rendered":"Mautic Community introduces multiple major improvements"},"content":{"rendered":"

A year on from the acquisition of Mautic, Inc. by Acquia<\/a>, it has been a year of significant change in the Mautic community.\u00a0 We have seen the establishment of a governance structure, the first in-person and virtual sprints, and shortly will see the first major release in almost four years with the stable release of Mautic 3.<\/p>\n

Throughout this time the Community Leadership Team<\/a> has been working closely with Acquia on building the foundations from which we can grow as a project and a community.<\/p>\n

We have some exciting updates to share with you today from across the project.<\/p>\n

A full time Project Lead appointed<\/h2>\n

Key to the success of any Open Source project is a strong leadership team who are engaged and dedicated to the growth of the project with a shared common vision.<\/p>\n

Today we are delighted to announce that – with the full support of the Community Leadership Team and DB Hurley – Acquia has appointed a new, full-time project lead. Community Manager Ruth Cheesley will be taking up the position of Project Lead.<\/p>\n

After leaving Acquia, DB Hurley scaled back his participation in the Mautic community and felt it was in Mautic’s best interest to have a full-time Project Lead.\u00a0 He will continue to act as an ambassador for the Mautic project. We are grateful for DB’s leadership and having guided us this far.<\/p>\n

Ruth has been involved with Mautic for a long time, and is excited about the opportunity to take up the baton from DB.<\/p>\n

This will mean some changes to the governance structure which are outlined here<\/a>.<\/p>\n

Setting the direction for Mautic<\/h2>\n

As a community, our underlying mission is to help people succeed with Mautic. Everything we do as a project aligns with this vision.<\/p>\n

We have six areas we are currently focusing on – ways we are helping people to be more successful with Mautic.<\/p>\n

    \n
  1. Develop the features and functionality <\/strong>so that Mautic becomes the tool of choice for Marketing Automation, and the market leader in this space<\/li>\n
  2. Improve the ease of use<\/strong> for marketers<\/li>\n
  3. Improve the stability<\/strong> and reliability of Mautic<\/li>\n
  4. Improve the way we support<\/strong> people to succeed with Mautic<\/li>\n
  5. Enable organisations to scale<\/strong> Mautic as they achieve success<\/li>\n
  6. Build a community<\/strong> that is self-reliant, welcoming, diverse and engaged<\/li>\n<\/ol>\n

    We have multiple initiatives and projects which we will be sharing – some today and some over the coming weeks – all of which contribute toward our mission.\u00a0 The first of these initiatives from the Product Team follows below.<\/p>\n

    Updates from the Product Team<\/h2>\n

    With the launch of Mautic 3, the Product Team will be making some changes to move us toward our vision of helping people succeed with Mautic.<\/p>\n

    We hope that we explain them fully below, however if there are any unanswered questions we will be running a series of live discussions and Q&A sessions where you can ask questions.<\/p>\n

    Release strategy and cadence<\/h3>\n

    Mautic 3 is the first major release in nearly four years. Between Mautic 2 and Mautic 3 there hasn’t been a clear cadence to the releases.<\/p>\n

    This creates challenges for everybody who relies on Mautic.<\/p>\n

    Organizations who rely on Mautic don’t know when to expect updates, which makes it very difficult for them to plan maintenance windows into their business cycles.<\/p>\n

    Community contributors who are submitting fixes and features don’t know when pull requests are going to be merged, or which releases they should be aiming for when they are creating their contributions.<\/p>\n

    Users of Mautic do not have forewarning of when to expect an update, or when features that they really need are likely to be delivered.<\/p>\n

    We appreciate that this not only causes confusion and frustration, but also makes it difficult for people to adopt Mautic when there is such uncertainty.<\/p>\n

    As a result the Product Team has decided to implement some changes to the way that we release updates for Mautic.\u00a0 We follow semantic versioning in our releases, for more information please read semver.org<\/a>.<\/p>\n

    Monthly patch releases<\/h4>\n

    We will be making a patch release every month. Patch releases include bug fixes only.<\/p>\n

    An example of a patch release would be 2.15.1<\/strong>, 2.16.2<\/strong>, 3.0.1<\/strong>.<\/p>\n

    Quarterly minor releases<\/h4>\n

    Every three months we will issue a minor release. Minor releases can include features which do not break backwards compatibility, and bug fixes.<\/p>\n

    An example of a minor release would be 2.15<\/strong>, 2.16<\/strong>, 3.1<\/strong>.<\/p>\n

    Yearly major releases<\/h4>\n

    A new major release will be made any time there are backwards compatibility breaking changes ready for release.\u00a0 We estimate a new major release every few years, but the exact frequency will depend on Mautic’s dependencies (e.g. Symfony, jQuery, etc).<\/p>\n

    As an example, we will need to upgrade from Symfony 3 to Symfony 4 or 5, well before Symfony 3 is end-of-life.\u00a0 The upgrade from Symfony 3 to Symfony 4 or 5 will likely require us to release a new major version of Mautic.<\/p>\n

    Major releases may include backwards compatibility breaking changes, features and bug fixes. An example of a major release would be Mautic 2<\/strong>, Mautic 3<\/strong>.<\/p>\n

    Anticipated release schedule<\/h4>\n