Philip Yarra wrote:

>On Wed, 25 Jan 2006 08:50 am, Chris Browne wrote:
>  
>
>>I haven't heard a *peep* as to issues still outstanding on 1.1.5, so
>>methinks it's time to go 'release-o-matic' on it...  Peter was the
>>last one to gripe about some things, and it has been a whole week
>>since then.
>>    
>>
>
>I've had no response to these issues I've raised:
>http://gborg.postgresql.org/pipermail/slony1-general/2006-January/003632.html
>http://gborg.postgresql.org/pipermail/slony1-general/2005-December/003557.html
>http://gborg.postgresql.org/pipermail/slony1-general/2005-December/003556.html
>http://gborg.postgresql.org/pipermail/slony1-general/2005-December/003558.html
>
>I figured there wasn't much point continuing to test if the results weren't 
>being read.
>  
>
Bugs 1507, 1508, 1511, and 1512 have been filed; they're not being lost.

Some of them would involve changing how the build process works, which
is something we are NOT going to do in the 1.1.5 cycle, because that is
pretty well guaranteed to break RPM packaging, which gets lots of people
all exercised.

They are excellent things to fix up for 1.2, which is what will start
proceeding when 1.1.5 is out...