It's been a week and more since release candidate time; the goal was to get a release out soon after the candidate. All the to-do items noted when the candidate was released have been satisfied, except a fancy graphical logo which should be the work of a day at most and seems to be basically blocking on a consensus as to what it should be. I'm afraid that if we spend too much more time polishing and hemming and hawing over this, we'll 1. never get it done, and 2. lose contributors through disaffection. Heaven knows I've done as much as I usefully can on the current release, and there's only so many times you can play it through looking for typos in a row before it gets rather tedious.
This being said, I would like to propose that we simply set a date for release, very soon, and on that date just zip up what we have and call it good. Getting a release out (and properly publicized in the right places) will inject some vigor into the project, free up the current contributors to work ahead with new things rather than endlessly going over the same content, and possibly even attract some new help.
It seems reasonable to expect release by next Friday, the 18th of May. Unless there's obvious and significant objection, we should plan to drop a release on that date. The current repository contents are quite good; a graphical logo would enhance the experience, but the current text version is serviceable, and there are no other major outstanding issues that I am aware of. We need to move forward and actually get something out and public.