From: Ron Mayer <rm_pg@cheapcomplexdevices.com>
Subject: Re: Release notes introductory text
Date: Fri, 12 Oct 2007 10:37:33 -0700
Organization: Hub.Org Networking Services
Lines: 18
Message-ID: <470FB0DD.2080104@cheapcomplexdevices.com>
References: <200710112004.l9BK4eq03596@momjian.us>
	<470E40B2.EE98.0025.0@wicourts.gov>
	<20071011165148.045f827c@scratch> <15467.1192152680@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
To: Tom Lane <tgl@sss.pgh.pa.us>
User-Agent: Icedove 1.5.0.12 (X11/20070730)
In-Reply-To: <15467.1192152680@sss.pgh.pa.us>
To: pgsql-hackers@postgresql.org

Tom Lane wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
>> With respect to you Kevin, your managers should wait. You don't
>> install .0 releases of "any" software into production without "months"
>> of testing. At which point, normally a .1 release has come out anyway.
> 
> How exactly do you expect the software to get from a .0 to a .1 release,
> or to have addressed the bugs that might bite you when it does get to .1,
> if you aren't helping to test it?

In most environments I've seen, developer and QA systems don't hesitate
to move to .0 releases (or even beta).   I agree with Joshua that it's
nerve wracking to move _production_ systems to .0 releases from most
software vendors.

> Now I realize that you did say "test" above, but way too often I see
> this sort of argument as a justification for doing nothing and expecting
> somebody else to fix it.