Body:
This is a busy time for me, with three major peojects on the boil: extensions (standard class extensions), rj, and stdlib-doc. They have some interdependencies which I want to detail here so that interested people can have an idea of what might happen and when.

The main outstanding issue for rj is to generate lots of documentation for it. I'm sick of doing it by hand, so I need a tool that can be told which stdlib files to convert (via RDoc and RImport) for rj. Now that shouldn't be too hard, but which files should I set it on? Well, that's what the stdlib-doc project is for.

stdlib-doc records the documentation status of the standard library. It can therefore be used to generate a file list for rj, based on how advanced the documentation it. Problem is, I haven't completed the tools required. I've started, but got distracted on extensions because ... well, it was "nearly done" and contains some methods I need for stdlib-doc.

extensions, thankfully, has reached a milestone now, with its v0.2 non-release (it's available through CVS only). I've just got to finish the unit testing for IO methods, and v0.2 will be cemented in a release. After that, I'll focus on the other projects, which will allow time to settle on some new extension methods.

So, to summarise.

extensions is ready to play with and downloadable via CVS (everything's good except the IO methods).

stdlib-doc is not in CVS yet, but I have invested many hours in it and am happy with progress. Before long, the CVS will be available, containing the data and tools needed to find the latest documentation status. Then work will begin on preparing packaged HTML documentation for the standard library.

rj is also ready to play with via CVS, version 0.2.4. It is useful as it stands, but a little messy (a bit of moise, not enough signal). The job of cleaning up the mess will begin very soon and I expect to release v0.3 in file form in the near future.

A final note, just to cover the vim-ruby project. Doug has made many syntax highlighting improvements since the project began, and these will see the light of day in a release soon. There'll be a development release first, then a user release. If anyone would like to help with the installer (Hugh Sasse made a good start), I'd be very grateful.