Jane Wells has announced on the WordPress.org development blog that the 24 hour has-patch marathon is now underway. The reason it’s called has-patch is because in trac, when someone submits a patch, the tags ‘has-patch‘ is added to the keyword field making it easier to sort through those tickets which actually have a patch.
During the next 24 hours, the core developers will be evaluating patches that have been tested and committing those that are up to par.
Grab yourself a copy of the nightly build to make sure you’re using the right version, then head over to Trac and start looking at the has-patch* tickets. Pick a ticket, download the diff, test it out on the browsers/platforms you have available, and write a comment about the results in the ticket’s comment thread. Move on to the next ticket. Do as many as you can over the next 24 hours.
Next Monday, Jane will publish the results of the marathon and in her message to the testers mailing list, she upped the incentive on contributing to this event:
When I put up the results of the marathon on the dev blog on Monday, I’ll also link to the top 5 testers from the 24-hour marathon period (measured by number of patches tested/commented in trac treads).
Hopefully, all goes well and if I can find the time, I’ll see if I can do a bit of testing on a patch or two. Last but not least, WordPress 2.8 is now feature frozen.