>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3572872. --> Reported by: [maddyt](https://www.drupal.org/user/3843187) >>> <p><strong>Update Summary: </strong> QA Weekly Meeting 11th February<br> <strong>Check-in Date: </strong>02/11/2026<br> <strong>Additional Collaborators: </strong> Zoocha<br> <em>Metadata is used by the <a href="https://www.drupalstarforge.ai/" title="AI Tracker">AI Tracker.</a> Docs and additional fields <a href="https://www.drupalstarforge.ai/ai-dashboard/docs" title="AI Issue Tracker Documentation">here</a>.</em><br> [/Tracker]</p> <p><strong>Summary</strong></p> <p>This ticket summarises key decisions and next steps for the Drupal Pod AI QA project as it moves toward wider community visibility.</p> <hr> <p><strong>Decisions</strong></p> <p><em>Aligned</em></p> <ul> <li> <strong>Default Version Compatibility</strong><br> Drupal Pod will default to the latest <em>compatible</em> combination of CMS/core and AI modules when no version is specified, reducing build failures and improving first-time user experience. </li> <li> <strong>Consult Drupal Forge Before Launch</strong><br> A discussion with Drupal Forge will take place prior to community promotion due to expected increases in resource usage. </li> <li> <strong>AI Agent Compatibility Bug</strong><br> A bug ticket will be logged to address version compatibility issues affecting AI agents. </li> <li> <strong>Project Maintenance</strong><br> Maintainer permissions have been updated to support ongoing development and administration. </li> </ul> <p><em>Needs Further Discussion</em></p> <ul> <li> <strong>QA Ticket Structure</strong><br> A proposed structure for automated tests, regression checks, and standard QA has been drafted. Guidance is needed on how QA-generated improvements should be managed within the backlog. </li> </ul> <hr> <p><strong>Key Points</strong></p> <ul> <li> <strong>Documentation</strong><br> Initial documentation has been tested successfully. Documentation should live on the project page and align with main AI initiative guidance. </li> <li> <strong>Version Handling Improvements</strong><br> The system currently pulls the latest CMS version by default, which can cause incompatibility with certain AI agent versions. A small update will ensure compatible versions are selected automatically when unspecified. Clearer feedback for failed builds is also desirable. </li> <li> <strong>QA Structure (Draft)</strong> <ul> <li>Main ticket for Automated Test Candidates (with subtasks).</li> <li>Separate tickets for Module Updates / Regression Checks.</li> <li>Defined approach for Standard QA on in-progress work.</li> </ul> <p> Further clarification is needed on when new tickets should be created versus keeping findings within the originating QA issue. </p></li> <li> <strong>Upcoming Work</strong> <ul> <li>Create tickets for auto-populating keys and environment auto-expiry.</li> <li>Log and track existing bugs.</li> </ul> </li> </ul> <hr> <p><strong>Next Steps</strong></p> <ul> <li>Update and create required feature and bug tickets.</li> <li>Log the AI agent compatibility issue.</li> <li>Share and review the proposed QA ticket structure and confirm backlog handling approach.</li> <li>Organise a call with Drupal Forge prior to launch.</li> </ul> <hr> <p><strong>Overall Direction</strong></p> <p>The tool is considered useful and close to ready for broader exposure. Immediate priorities are stabilising version defaults, clarifying documentation, and aligning on QA backlog management before public launch.</p>