X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP
	id 95BFAD1C91B; Tue, 18 Nov 2003 04:08:23 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024)
	with ESMTP id 37289-06; Tue, 18 Nov 2003 00:07:52 -0400 (AST)
Received: from houston.familyhealth.com.au (fhnet.arach.net.au
 [203.22.197.21])
	by svr1.postgresql.org (Postfix) with ESMTP
	id 057B9D1B550; Mon, 17 Nov 2003 23:56:03 -0400 (AST)
Received: from familyhealth.com.au (work-40.internal [192.168.0.40])
	by houston.familyhealth.com.au (8.12.9p1/8.12.9) with ESMTP id
	hAI3tQoD075184; Tue, 18 Nov 2003 11:55:26 +0800 (WST)
	(envelope-from chriskl@familyhealth.com.au)
Message-ID: <3FB99903.4090809@familyhealth.com.au>
Date: Tue, 18 Nov 2003 11:58:59 +0800
From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.5) Gecko/20031013 Thunderbird/0.3
X-Accept-Language: en-us, en
MIME-Version: 1.0
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>
Subject: Re: Release cycle length
References: <Pine.LNX.4.44.0311180329330.639-100000@peter.localdomain>
	<3FB988B8.1050904@zeut.net>
	<87smkmgyn7.fsf@mailbox.samurai.com>
	<3FB992C9.6020207@familyhealth.com.au>
In-Reply-To: <3FB992C9.6020207@familyhealth.com.au>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Archive-Number: 200311/932
X-Sequence-Number: 47220

> 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