We’re getting ready to prepare Mautic 4! This will the fourth major release of Mautic, with some exciting new features, like the Mautic Marketplace and New Email Builder!
We need your help!
The more community contributions we get (code, documentation, etc.), the more awesome features we can bring to our users. More on that in the “How can I contribute?” section below.
This is our very first Mautic 4 sprint. This will be all about laying the technical groundwork for Mautic 4 to build new features on. Without going into too much detail here, the most important aspect here is upgrading our technical dependencies (like Symfony). You likely won’t see new features yet in this sprint.
Required skill sets:
Developers (code + review)
Technical writers (documentation), to update our developer docs and user-facing docs where applicable. There will be breaking changes that we need to document!
Beta Sprint (April 23 - 25) - Completed
In this sprint, we’ll get more focused on user-facing features. It’s probably the most exciting of them all, because some shiny new functionality will come to life here! It also means that we’ll need more different skill sets.
Required skill sets:
Developers (code + review)
(non-technical) Writers for end-user facing documentation (“how does feature X work, how can I use it best?”)
Technical writers for developer documentation (walking through the existing docs, creating demo plugins, testing the API, all to verify if our docs are up to date)
Marketers to test the new features and help us prepare the communication strategy/material for Mautic 4
This sprint will be for fixing rough edges in Mautic 4. It’s the most crucial one, because it’s the final sprint before the general release. Smoke testing is key here. We’ll also be extensively testing the upgrade path for Mautic 3 to 4. In short: getting ready for release!
After this sprint, no further features and/or bug fixes will be considered (“freeze period”), except for critical, release-blocking bugs.
Required skill sets:
Same as the Beta Sprint
Testers! Both technical and non-technical. Test as many aspects of Mautic as possible, and try to break things on purpose. We want Mautic 4 to be bullet-proof! Who doesn’t want to do that?
General Availability Sprint (May 21 - 23) To be rescheduled
These are the final days before release (May 24 June 28). We’ll prepare all marketing and support channels for the release. There shouldn’t be any more release-blocking bugs at this point, but the sprint can act as a buffer for final bug fixes in the worst case.
Required skill sets:
Same as the Release Candidate sprint, but a focus on marketers and technical support
Take a look at the sprint planning document here - this will be a living doc throughout the entire release process with the currently active sprint at the top of the page
Join the kick-off calls - we hold one at 10am CEST and 4pm CEST, and a wrap up call at 8pm CEST on each day of the sprints
Take a look at the sprint board (if you need access to Jira please ask in the Mautic 4 channel on Slack) and assign yourself to any tasks - please ping in Slack so we can ensure that work is not being duplicated!
It isn’t released yet, so you can’t, afaik. If you want to be testing then please use ddev locally and join #mautic-4 on Slack (https://mautic.org/slack) too keep up to date.
We have a sprint this weekend if you’d like to help with the docker image?
We are running late with the releases due to the very small number of people who are helping with testing, fixing bugs etc.
Please help by testing the beta version locally in a development environment and reporting any bugs you might find at github.com/mautic/mautic/issues (check first to make sure they are not already reported) and join #mautic-4 on Slack (https://mautic.org/slack for an invite)
Realistically we are looking at a Release Candidate possibly around the 14th June and the full release after Mautic Conference Global, probably around the 28th June.
Sorry for the delay but we have some bugs that need to be fixed and a couple of issues with the builder which need to be addressed, and a very small number of folks working on it (who are also working on Mautic Conference Global!).
While making the Release Candidate release this evening, we have come up against a fatal error with testing the upgrade (which happens as part of the release) - this appears to relate to the removal of support for OAuth1.
We are looking into a fix for this, until there is a fix we are unable to make the release.
Please bear with us while we work through this issue!
I am also getting the following schema error when trying to upgrade t 4rc which also appears related to oauth1
[2021-07-05 12:11:14] mautic.NOTICE: Doctrine\DBAL\Schema\SchemaException: There is no table with name ‘mauticdb.oauth1_access_tokens’ in the schema. (uncaught exception) at /config/www/mautic/vendor/doctrine/dbal/lib/Doctrine/DBAL/Schema/SchemaException.php line 34 while running console command doctrine:migrations:migrate
An update for those of you keenly awaiting a release today … I’m sorry to disappoint you but we still have some outstanding issues which need to be addressed before we can make the release.
Unfortunately we simply do not have enough developers and testers picking up these issues which means that we are not able to make the progress we need in order to make the release.
When we have a clearer idea of timelines, we will make an updated release date known.
We do really appreciate the frustration of having the dates keep getting pushed back, but we do not want to make a release which we know introduces bugs that would cause you problems.
@rcheesley and everyone else contributing take as much time as you need to do it properly. The worst thing that can happen is to make available a buggy release especially a major version release.
Unfortunately don’t have time to contribute with testing but I highly appreciate everyone working on this.
Thanks @poetry - we are going as fast as we can! It’s a challenge when folks are super busy in their work, as there is less time available for community contributions … on top of covid, holidays etc. We are making progress though thanks to some folks stepping up to help so hopefully not too far away!
I’m sure you get this all the time but I want to ask… All online sources showing a potential date for the General Release of 4.0.0 are old dates. Any thoughts on when we could look forward to seeing the General Release?
I’m eager for the fixes to the builder. So far, in our testing, everything about the RC is working great, with the exception of builder issues.
@PowerBoot I am just back from vacation, but we have I believe three PRs which are blocking the release. I will catch up with the Product Team today and should then have a better idea of timelines!
We need your help!
PR needs testing 
Fix email issue that was introduced recently in Amazon SES API 