Sorry for the unscheduled downtime on the WordPress Version Check webservice earlier but I had to shut the power off quickly on this server after we discovered the central heating system was leaking quite close to some of the main circuitry. It’s all up and running again now and wpbot should also be chatting away back in #wordpress. Now we just need to buy the replacement part for the primary heating circuit so that we can have hot water again 🙁
Category: WordPress
All things wordpress
my new favourite one liner
Well last weeks bug hunt went well by all accounts we managed to convince Ryan to make 30 commits and about 100 tickets were closed. During the process of testing all these patches I found a new favourite one-liner for working with trac and patches:
svn revert -R * && curl "trac-patch-raw-fileurl" | patch -p0
This enables you to download a patch direct from the trac web interface and apply it against your local svn checkout ensuring to revert any other local changes first. For example using this with the patch attached to ticket 3110:
svn revert -R * && curl "http://trac.wordpress.org/attachment/ticket/3110/3110.diff?format=raw" | patch -p0
pjw-mime-config v0.90 released
A while ago I released a simple plugin which allows you to manage the mime-types supported by the WordPress inline-uploader. This plugin worked well for most people baring a issue with php shorttags which made it break some sites. However, some people requested an update to the plugin to support adding a large list of mime-types from a file. I am proud to announce that finally after many months of sitting there 95% finished I am ready to release this plugin update.
It’s bug hunt time.
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 :-).