>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3575717. --> Reported by: [maddyt](https://www.drupal.org/user/3843187) >>> <p><strong>Update Summary: QA Meeting - 25th Feb 2026 </strong><br> <strong>Check-in Date: </strong>02/25/2026</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <ul> <li>Weekly QA Meeting to discuss updates around Drupal Pod Development and General QA Processes</li> </ul> <h3 id="summary-proposed-resolution">Points Discussed</h3> <ul> <li>QA compatibility scenario testing start The QA team will begin testing the matrix of different compatibility scenarios for AI modules (e.g., AI context, AI search) starting next Monday.</li> </ul> <ul> <li>Compatibility scenarios documented in QA issue A list of specific compatibility testing scenarios will be added to the QA project issue by Tawny for QA team members to pick up.</li> </ul> <ul> <li>1.3 release full script testing Testing for the 1.3 release will be run by the QA team next week using the full test script Marcus will provide.<br> Flagging major QA tickets in channel Major tickets requiring QA attention must be flagged in the AI QA channel, in addition to using the standard needs QA tag.</li> </ul> <ul> <li>Bi-weekly patch testing schedule defined The patch testing schedule is set to run bi-weekly (every other Wednesday) to check for unexpected regressions.</li> </ul> <ul> <li>Aimed shift in Drupal to smaller, more frequent releases featuring one or two features to reduce extensive testing requirements.</li> </ul> <h3 id="summary-remaining-tasks">Remaining tasks</h3>