Part 1: Run the "*Command(s) to detect..." mentioned in the description 1-1: upgrade.php files not having the upgrade line Run the command to detect all the upgrade.php files not having the upgrade lines: find . -name upgrade.php | xargs grep -l 'function.*xmldb_.*_upgrade' | grep '/db/' | xargs grep -L 'Automatically generated Moodle v4.4.0 release upgrade' Confirm that nothing is returned 1-2: Incorrectly added upgrade lines Run the following commands to detect that we have not added the lines to incorrect files: grep -lr 'Automatically generated Moodle v4.4.0 release upgrade' * | grep - v '/db/' grep -lr 'Automatically generated Moodle v4.4.0 release upgrade' * | xargs grep -L 'function.*xmldb_.*_upgrade' Confirm that nothing is returned 1-3: Check upgrade lines added after upgrade steps made after the release Run the command to detect if the lines have been added after a post-release upgrade step. If there are upgrade steps found verify that all of them were already there on the day of the release and have not been introduced later (you can look for differences between the release v4.4.0 and the current master to verify that) export rel= "4.4.0" && export ver= "202404" && find . -name upgrade.php | \ xargs grep -B25 "Automatically generated Moodle v${rel} release upgrade" | \ grep "upgrade_.*_savepoint.*${ver}" Confirm that if any upgrade.php files are returned, the date indicated in the " upgrade_xx_savepoint() " call are not after the 4.4 release date of 20240422. Part 2: Check all upgrade scripts with upgrade comment Check all upgrade scripts have the 4.4.0 comment before the return with: find . -ipath '*/db/upgrade.php' | xargs grep -B4 'return true;' Random exceptions: Some upgrade scripts could be missing the comments before the return. Surely it's because some new steps already have been introduced after the release. Verify the comments are present in the correct place (before those new steps). Part 3 This should return nothing too or the it will return the same exceptions mentioned in Part 2 or in 1-3: for u in ` find . -name upgrade.php | grep 'db/upgrade' `; do grep -B4 'return true;' "$u" | grep "Automatically generated" > /dev/null ; if [ $? - ne 0 ]; then echo "$u" ; fi ; done Part 4 Verify that the differences between the stable branch and master continue being 100% the same after the patch than before it (aka. the patch is 100% the same for both branches). Note that this is not true under parallel development , or when versions already have diverged, so skip this step if that's the case.