Propose new Mautic features

Release planning meeting for the Mautic Community.

We will be reviewing feature proposals and assigning them to milestones, while also prioritising PRs and issues for the forthcoming three releases.

All PRs and issues to be considered must:

1. Have all automated tests passing
2. Maintain, or ideally improve, automated test coverage (as measured by Codecov)
3. Have documentation updates already created and reviewed by the Education Team
4. Be in a mergeable state (have no file conflicts)
5. Have clear instructions in the pull request description for testers to follow which will allow them to:
6. Reproduce the bug (if the pull request is a bug fix)
7. Test the fix / test the feature
8. Understand the areas that the pull request may impact to facilitate full and proper testing

Attendees

Ruth Cheesley

John Linhart

Joey Keller

Apologies:

Mattias Michaux

Notes:

[Security team discussion redacted]

• There was a necessary package update to fix CI/CD in the 4.4 branch, this PR was merged to unblock testing of PRs on 4.4
• 5.1 release will likely be made mid-April, aiming for the 16th April currently.
• We need to try to fix the DNC/bounce situation in this release if possible. Joey will share the link to the PR once the PR is up.
• After the 5.1 release we will go back to the monthly patch release and quarterly
• We will schedule minor releases quarterly, but with the option for us to make a minor release sooner if there's enough PRs merged

Mautic 6 

• Ruth suggests that we should specify the minimum requirements that are needed to release 6, and then work to that, rather than have a specified date. This is the group where we make those definitions
• John wants us to be supporting Symfony 6 before the end of active support of 5.
• John suggested creating a PR with Rector supporting 6 rules to see how much work is going to be needed.
• Joey mentioned the users are struggling most with the lack of email transports - it's blocking people from updating to 5.
• In the future we should make sure we don't make this mistake again - perhaps we could fundraise for those things that are not getting done in time.

Minimum requirements:

• Symfony 6.4, PHP 8.2
• Marketplace out of Beta - we have some GSoC projects which might support this.
• Some discussions about the install process / composer / docker / etc.

Ideal:

• Symfony 7.1, PHP 8.3

ACTIONS:

• Make a PR for Symfony 6.4 and 7.1 support and see what's going to be involved / make a call on what's feasible for the Mautic 6 release timeline (release freeze middle of September)
• Communicate about upcoming releases - Lenon to communicate mid-week what people can expect and to manage the process of releasing, and work with John/Mattias to make the releases.
• Joey to share the link to PR fixing bounce/DNC issues when it's available