Note: You are currently viewing documentation for Moodle 2.4. Up-to-date documentation for the latest stable version of Moodle may be available here: Weekly Code Review.

Development:Weekly Code Review

From MoodleDocs

Moodle has a weekly process of code review in the stable branches to help improve the quality of stable packages and to help detect any regressions that may have occurred in stable code.

Here is the process for testers and developers:

Every Tuesday

Everyone should look at the latest bugs needing review:

 Moodle 1.9 stable:  1.9.x Needs QA review

(Make sure you can see the QA Assigned column)

Grab any bug that:

  • is from the last week
  • you did not fix
  • does not have a QA assignee yet

and claim it by editing the bug to add your name as QA Assignee.


Test the fix

  • Read the comments
  • Look at the patch atatched to the tracker
  • Try the feature out to make sure it works as advertised
  • Post new comments (or talk on Moodle HQ) if you need clarification


Mark the fix as reviewed

  • When you are satisfied, simply change the status from Resolved to Closed

Every Wednesday

  • The download site will automatically tag the whole current stable codebase (eg MOODLE_19_WEEKLY) and then build download packages