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    

Actions from previous meeting:

Notes from last meeting: https://community.mautic.org/processes/roadmap/f/44/meetings/39

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) [Done]
• 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. [Done]
• Joey to share the link to PR fixing bounce/DNC issues when it's available [I think not yet done?]

Notes from this meeting:

• Mautic 6 is pending on some work that Adrian Schimpf is doing to improve the JS building - we want to get this into the release
• John also spent some time working on removing the legacy builder which we want to remove in 6.0. This will also mean that the old legacy-only builder themes will need to be considered - do we leave them or remove them? Joey said that removing would be a problem if form uses the theme so we should leave them for now.
• Discussion on whether to release 6.0 with what we have (basic Symfony update to 6.4 and some small number of features) and have Adrian's work pushed to 7.0. Give Adrian a week to get back to us and then have a deadline for the code to be merged.
• Deadline for 6.0-beta release 24th Jan to release on 27th Jan (Monday) - there are 12 open PRs currently.
• 5.2.2 release will be on 28th Jan.
• Some discussions about concerns around not having any feature releases for three quarters (6.0 through to 7.0) - Joey suggested we can do some work highlighting new features from 5.2 onwards.
• We could release the 7.0 General Availability early if we have everything that is required. We would have to make sure we keep up with Symfony releases in minor releases, as they're only on 7.2 currently.
• We'd need to make sure we have any BC breaking changes and also any deprecations ready.

Actions from this meeting:

• Joey can put some comms together about the upcoming releases
• John will ask someone via #t-product to make a PR for Mautic with Symfony 7.2 and PHP 8.4 based on the 6.x branch
• Decide what to do re. Adrian's contributions - if he can't recover his work we'll release 6.0 as-is on the freeze date, and his work will go to the 7.x branch when created.
• Check in with the education team about updating the documentation to support the 5.2 UI changes - maybe with a sprint of some kind?