... are still there, even if I don't blog about every single bit all the time. Most of the packages I care about are in good state, I even did jump on board of irssi co-maintaining and got its bugcount down a fair bit (though I won't rest at this stage, there are still some to go) and did jump onboard of the pkg-games Team.
... which brings me to wesnoth. For quite a while I am tracking the stable releases (1.2.x) of wesnoth in unstable while the development releases (1.3.x) are followed in experimental. With the upcoming stable release 1.4 this though will change. The development branch is feature frozen and thus will be (propably) compatible with the next stable release, and furthermore the current stable release isn't expected to receive any further update. My plan is thus to upload the next development release directly to unstable. If you want to give it some additional testing before that happens pull the package from experimental now and give your feedback, thanks.
Furthermore I am also tracking some packages for backports.org. I usually do the packaging of it almost synchronous to its upload into unstable although it is only allowed onto backports.org when it entered testing. For the timegap in between you can usually find it on my website repository. Directories that aren't empty there have some upload to backports pending and you can feel free to test the packages and send me feedback on them. Currently this includes bacula, slony1 and postgresql-8.3.
One last note, finally it happened: apache1 isn't anymore. There were two packages left in testing until recently which got their removal requests adjusted. Thanks to everyone involved in keeping track of this and helping cleaning up the archive.