It’s time to dig out that can of RAID and get bug hunting again. Lloyd suggested another bug hunt on the wp-testers list and Ryan has suggested a time 01:00 UTC on August 30th 2006 (Although due to work commitments it likely I won’t make the Bug Hunt until 17 hours later ). For more information about the bug hunt process you can read the questions and answers section of the WordPress Bug Hunts page on the codex.
If you need some help in understanding the process of using subversion to access the WordPress code and applying or making patches then I suggest you read through one of the few articles about working on WordPress – Specifically there are Marks’s instructions for working on MAC OS X or Linux and my instructions for working with Tortoise SVN on Windows.
So what bugs are we hunting this time? Well my personal preference would be for people to work through the lists of Has Patch tickets, i.e. those which someone has coded a fix for, and test the patches against the current trunk code adding bg|tested and/or bg|commit to the keywords for the ticket so as to show that the patch works as described and is ready for commit to the WordPress code. After all we have far too many patches, 187 at present, sitting there that either need committing or rejecting.
Hopefully then Ryan can work through the list of Commit Candidate tickets committing them to the code .