Campaign Library initiative

Project name: Campaign Library Phase 1
Status: 🟠 Minor delay

We're maintaining the "minor delay" classification for the Campaign Library Phase 1 project.

The team is currently working through the code review process, during which we made the strategic decision to defer bundle structure changes until after the testing phase. Team collaboration remains strong, though our commitment to high quality has extended our timelines somewhat.

We are approaching the testing phase but have not yet begun. Some illness within the team, coupled with the advent of Easter bank holidays, has further extended our com...
Saiba mais

Hi all

Project name: Campaign Library Phase 1
Status: 🟠 Minor delay

This week has been slower than anticipated in terms of overall progress. The aim had been to be well into the testing phase by now, but we’ve encountered some challenges finalizing the remaining tickets and meeting the required standards for unit and functional testing, particularly with PHPStan.

Midweek, we made the decision to hold off on starting the manual code review, as the relevant code was still undergoing changes to resolve outstanding issues. As a result, the code review has not yet begun, and we anticipate some back-and...
Saiba mais

Hi all

Project name: Campaign Library Phase 1
Status: 🟢 On target

Our goal for this week was to complete the intended development for Phase 1 of the Campaign Library project. As I write we have 3 open tickets with one in progress. The two tickets that are yet to be started I consider to be a lower priority (confirming that with the team) so I think we are in good shape to start with the testing phase of the work next week. 7 tickets have been completed in this sprint, including an extension of the API call to import campaigns using an attached file, and being able to import and export multiple ca...
Saiba mais

Hi all

Project name: Campaign Library Phase 1
Status: 🟢 On target

In our sprint review on Monday we talked as a team about how we would work through the last stages of the project: testing and code review. Unlike a lot of smaller enhancements to Mautic, this piece of work will be delivered as one large chunk of code, and so from a governance perspective is classified as a 'level 3' change, meaning it requires 2 testers from separate organisations and 1 code reviewer in order to qualify to be a part of the codebase. Mautic is fortunate to have an active community of people who are willing to volun...
Saiba mais