Re: Release cycle length

Christopher Kings-Lynne <chriskl@familyhealth.com.au>

From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Neil Conway <neilc@samurai.com>, "Matthew T. O'Connor" <matthew@zeut.net>, Peter Eisentraut <peter_e@gmx.net>, "Marc G. Fournier" <scrappy@postgresql.org>, PostgreSQL Development <pgsql-hackers@postgresql.org>
Date: 2003-11-18T03:58:59Z
Lists: pgsql-hackers
> eg. Someone who just knows how to use postgres could test my upcoming 
> COMMENT ON patch.  (It's best if I myself do not test it)  Someone with 
> more skill with a debugger can be asked to test unique hash indexes by 
> playing with concurrency, etc.

I forgot to mention that people who just have large, complex production 
databases and test servers at their disposal should be given the task of:

1. Dumping their old version database
2. Loading that into the dev version of postgres
3. Dumping that using dev pg_dump
4. Loading that dump back in
5. Dumping it again
6. Diffing 3 and 5

Chris