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 :-).
In preparation for the first WordPress Bug Hunt this weekend Mark Jaquith has written some excellent instructions on how he “does work” on WordPress on Linux / Mac OS X.
Skippy who is one of the hosts of the bug hunt was looking for a Windows version of Mark’s cheat sheet – So here or those of you using Windows the following instructions show you how to achieve the same things.
First of all you need to install an svn client, the svn client of choice on Windows has to be TortoiseSVN which is not only a subversion client but also includes patch application functionality and visual merge tools. Once you have installed TortoiseSVN you will now be set and ready. So here is the “Working on Windows” version on Mark’s instructions:
Read the rest of this entry »
This Saturday there is going to be the first “WordPress Bug Hunt”. The aim of the event is to blast through all the outstanding bugs in Trac marking fixed those already fixed and working on developing fixes for those that still exist.
Skippy recommends that you bring along a text editor and a fresh install of WordPress 1.6-ALPHA-2-still-dont-use a good way to do this is to setup a local install on your home computer for example using XAMPP if you are running Windows or using these instructions if you are on Mac OS X – It both cases don’t forget you want to install the latest svn version.
There is a dedicated IRC channel for people to meet up on on the day and discuss the bugs which is #wordpress-bugs on freenode.
You don’t need any coding skills or experience to turn up. Just being willing to attempt to test whether or not bugs still exist will make you very useful as some of the open issues date from v1.2 and earlier and have quite likely already been fixed.