I have checked in a fair "boatload" of patches supporting this and that; 
from my perspective, I think it starts making sense to look towards a 
1.1 release in the next couple of weeks.

On my side, there are a couple of places where I'd particularly like to 
see people banging on things to see if they break:

1.  Log shipping support

This is newly added, the ability to specify a log directory where files 
containing SYNC sets will be written.  It supports SUBSCRIBE SET, which 
means that you can take an empty schema, subscribe the node that you're 
using to collect the logs, and find that there are log files to populate 
things from there.  This is new, and therefore not of maximum maturity.

2.  A tuning of VACUUMing

I have added a function to the cleanup thread which looks to see if the 
earliest XID presently "in play" is the same one found last time.  If 
that is so, then there is no point in VACUUMing tables, as no data will 
be cleaned out.

I'm concerned that this may not "play properly" for XIDs > 2^31; having 
some extra eyes on get_earliest_xid() in cleanup_thread.c would be most 
useful.

It is seldom wise to release things on Friday; what I suggest is that 
people interested in the 1.1 release who are prepared to live a little 
on the "bleeding edge" take a peek and see if you can break it...

There have been a gratifying number of changes being contributed in; 
hopefully the floodgates will relent a bit so that we can see about 
preparing for a release in the near future.
-- 
<http://linuxdatabases.info/info/slony.html>