I'll put my hand up for doing the Windows build as well (the x64 buildbot has all the necessary bits and pieces installed). I know some HP people that I could rope in to install the resulting IA64 build and run rt.bat.
Notice that we both look for somebody to build the next 2.6/3.0 betas (see the subject), and the 2.5.3 rc and final release (assuming Anthony still has that plan).
I'd like to offer my Win2k8 x64 colo box for building Python installers. It's a Hyper-V instance with four cores, 4GB of RAM and plenty of disk space, and has just about every Microsoft-oriented development tool installed produced this decade (inc. Itanium compilers).
So, ideally, any committer that's interested in being able to produce the official Python binaries can drop me a note and I'll give them remote access. That way we've got a single 'build server' for producing releases, as well as multiple people with the capacity to perform such builds.
I'm probably biased because it's a freakin' expensive colo and I'm severely under-utilising the box (host is an 8-core 8GB monster), but I'd argue that a nominated build server is more desirable for official releases than someone's laptop.
(Even if we don't go down this path, if other developers would like remote access to the box just drop me an e-mail. I specifically acquired it to 'donate' to Python-oriented activities; no-one else has access to it.)