# Public Release of Mautic 7.0-Alpha? **URL:** \ **Category:** Development\ **Created:** [July 16, 2025, 3:34pm UTC](https://forum.mautic.org/t/public-release-of-mautic-7-0-alpha/36111 "2025-07-16T15:34:47Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![andrew\_c3](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/andrew_c3/32/13547_2.png) [@andrew\_c3](https://forum.mautic.org/u/andrew_c3)\ **Post date:** [July 16, 2025, 3:34pm UTC](https://forum.mautic.org/t/public-release-of-mautic-7-0-alpha/36111/1 "2025-07-16T15:34:47Z")
Hello, I’m eagerly awaiting the alpha release of Mautic 7 and I was wondering when its likely to be made public so I can begin testing it on our web platform ? I know its difficult to give an accurate timescale as its still being developed but I would appreciate an estimate i.e. one month, three months, six months etc… so I can plan ahead. How can I get involved in the alpha testing phase ? Thanks. ---
**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\ **Post date:** [July 16, 2025, 3:43pm UTC](https://forum.mautic.org/t/public-release-of-mautic-7-0-alpha/36111/2 "2025-07-16T15:43:49Z")
Hey @andrew_c3 great to hear you’re keen to test! At the Community Sprint in Prague last week, we merged the last PRs that were needed to bring Symfony 7 and PHP 8.4 support πŸŽ‰. You can pull the 7.x branch and test there: > **[GitHub - mautic/mautic: Mautic: Open Source Marketing Automation Software.](https://github.com/mautic/mautic)** > > Mautic: Open Source Marketing Automation Software. We recommend using DDEV to test locally: [https://mau.tc/tester](https://mau.tc/tester) We are aiming to make the release for the alpha once we have this PR merged which must go out in the alpha, you can help with that by testing/reviewing it: Campaign import/export: > > > | Q | A > | --------------------------------…------ | --- > | Bug fix? (use the a.b branch) | πŸ”΄ > | New feature/enhancement? (use the a.x branch) | 🟒 > | Deprecations? | πŸ”΄ > | BC breaks? (use the c.x branch) | πŸ”΄ > | Automated tests included? | πŸ”΄ > | User documentation | https://github.com/mautic/user-documentation/pull/361 > | Developer documentation | https://github.com/mautic/developer-documentation-new/pull/242 > > \## Description > > This proof of concept (PoC) implements the Campaign Library feature, focusing on the export and import of a single campaign entity without involving the UI. The goal is to demonstrate the core functionality of exporting and importing campaign data in a streamlined manner. > > \--- > \### πŸ“‹ Steps to test this PR: > > \#### 1. \*\*Exporting Campaigns\*\* > Use the following commands to export campaigns: > > \- Export campaign data in JSON format only: > \`\`\`bash > ddev exec bin/console mautic:entity:export --entity=campaign --id=1,2,3 --json-only > \`\`\` > > \- Export campaign data as a ZIP file: > \`\`\`bash > ddev exec bin/console mautic:entity:export --entity=campaign --id=1,2,3 --zip-file > \`\`\` > > The output files will be stored in the Docker container's temporary directory (\`/tmp\`). To access these files on your system, use the following commands to copy them to a local directory: > > \`\`\`bash > docker cp ddev-mautic-web:/tmp/campaign\_data.zip ../mautic/campaign\_data.zip > \`\`\` > > \#### 2. \*\*Importing Campaigns\*\* > To import the exported campaign data, use the following command: > > \`\`\`bash > ddev exec bin/console mautic:entity:import --entity=campaign --file=campaign\_data.zip --user=1 > \`\`\` > > \*\*Note:\*\* Before running the import command, the required files must be copied to the Docker container's temporary directory. Use the following commands to copy the files into the container: > > \`\`\`bash > docker cp ./campaign\_data.zip ddev-mautic-web:/tmp/campaign\_data.zip > \`\`\` > > \#### 3. \*\*Verification\*\* > \- Verify that the campaign data is correctly exported by inspecting the ZIP files in the system directory. > \- Ensure that the imported campaign data is successfully reflected in Mautic. > > \### πŸš€ Expected Results: > \- Export commands generate the appropriate files in the Docker container's temporary directory. > \- Import commands successfully import the exported campaign data into the system. > \- No errors are encountered during the export or import process. > > \### πŸš€ Jira Ticket: > https://mautic.atlassian.net/browse/CL-34 Also this one is a breaking change: > > > Remove Identify visitor by tracking url configuration settings usage > > > > | Q … | A > | -------------------------------------- | --- > | Bug fix? (use the a.b branch) | βœ”οΈβŒ > | New feature/enhancement? (use the a.x branch) | βœ”οΈβŒ > | Deprecations? | βœ”οΈβŒ > | BC breaks? (use the c.x branch) | βœ”οΈβŒ > | Automated tests included? | βœ”οΈβŒ > | Related user documentation PR URL | mautic/user-documentation#... > | Related developer documentation PR URL | mautic/developer-documentation-new#... > | Issue(s) addressed | Fixes #... > > > > \## Description > > > > > > > > > \--- > \### πŸ“‹ Steps to test this PR: > > Seems like we do not need this option in configuration. From some refactoring, contacts are identified by CT parameter by default with the line: https://github.com/mautic/mautic/pull/14974/files#diff-ff1cf0e25a20c2ebe5f252374318df2cb7aa36bb6c880db1a693f3e2e2e4ec8cL122 > > > 1. Open this PR on Gitpod or pull down for testing locally (see docs on testing PRs \[here\](https://contribute.mautic.org/contributing-to-mautic/tester)) > 2. Just check if tracking works like before The full milestone is here with other PRs we’d _like_ to get merged. Quite a lot only need one more test. > **[mautic/mautic](https://github.com/mautic/mautic/milestone/125)** > > Mautic: Open Source Marketing Automation Software. - mautic/mautic Once we release the alpha we’ll then have a beta and Release Candidate, the goal is to release General Availability by the end of the quarter.