Last updated 13 November 2016.

Once the patch is created, attach the patch file to a comment in the issue and change the status to “needs review”.

This will queue the patch for testing by the testbot and add alert other community members that the patch needs to be tested. The review by a community member could take a little while as most people are volunteering their free time while working full time jobs so please be patient.


By attaching a patch and setting the issue status to "needs review", the patch will be automatically queued for the testbot. The testbot does the automated regression testing for Drupal Core. It will do a setup and run all of the SimpleTests within the project.

Note: if the testbot doesn’t queue the patch, verify that the status has been switched to “needs review”. Also, check that the patch file name ends in .patch or .diff, and doesn't have the Drupal version in it (see note under the Attach field).

If the patch doesn’t pass, the patch information line in the issue will turn RED, and the issue status will be changed to "needs work". You should then review the patch and determine why it failed. Make sure that you can load the patch and run any SimpleTests locally that may have failed. (Note: run only the tests that failed; otherwise, it could take a LONG time to run all of the tests - leave that to the testbot.)

Community review

If the patch passes, its status remains "need review". It then needs to be reviewed by someone in the community. After verifying the functionality and suitability of the patch, the reviewer will change the issue status to RTBC (Reviewed and Tested By the Community).

Now, someone could comment on a "needs review" and leave the status the same, allowing for additional reviews.

It is NOT uncommon for the status of a patch to be reverted to "needs work". The quality and consistency of core work needs to be high, so never take this personally and try to learn why the work was suggested. If this happens, get a clean enviornment, download the patch, make the change and then upload another, new, patch.

Continue this process until the patch has both passed the testbot and has received the RTBC status.