What I want to do before 2.0 gets off of my desktop is put up a bug database. I’m kind of hesitant about using wp-plugins at this point because I can’t figure out how to get Tortoise SVN to checkout two projects to one working directory. Yeah, maybe I should just use two working directories, but I’ve already got WordPress installed so many times on this system it’s crazy…
Sorry if that’s all greek.
Anyhow, 2.0 is WP1.5-only. 1.1 will stay around for the 1.2.x’ers. There are too many good plugin hooks in 1.5 to have to back-port.
This post is also not a promise that the 2.0 code will ever see release. I’ve got a billion projects going on right now, some WordPress, some not. The OSA project (augmented spam filtering for WP1.5 with p2p spam wordlists) is pretty high on my priority list right now. I want people to test the GeoPlugin, which is a replacement for the Geo features that you lose when you upgrade from 1.2-1.5. I’m considering a small plugin for FFAF this month that limits user posting to certain categories based on their user level. I’ve got this other crazy project that’s like a micro web server that you run on your desktop to enable file-sharing. I just got a contract offer yesterday (for $$) to maintain a site that I might actually decline so that I can finish all of this crap and clear my mind of it. And every time I stop by the forums I end up reading/replying for hours instead of doing actual coding… Gah!
Busy busy.
But yeah, I’ll take on testers as soon as I get some of the technical bits (like, how to version control/distribute the plugin) taken care of.