In-Reply-To: <200704301004.25297.josh@agliodbs.com>
References: <200704270313.l3R3DwF16449@momjian.us>
	<1177792836.3663.61.camel@silverbirch.site>
	<46349EF4.2010304@enterprisedb.com>
	<200704301004.25297.josh@agliodbs.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <7821E6AA-E46D-46E1-95FC-33BD16085532@decibel.org>
Cc: pgsql-hackers@postgresql.org
Content-Transfer-Encoding: 7bit
From: Jim Nasby <decibel@decibel.org>
Subject: Re: Feature freeze progress report
Date: Tue, 1 May 2007 13:27:40 +0100
To: Josh Berkus <josh@agliodbs.com>

Two more ideas for the manager, now that we seem to have consensus to  
build one.

On Apr 30, 2007, at 6:04 PM, Josh Berkus wrote:
> -- We could save the patches by applied date and index them, and  
> then have a 
> place to point users when they ask: "When was X fixed?  Do I *have* to
> upgrade to 8.1 or just 8.0?"

This should also make doing the release notes substantially easier,  
though since there's probably some stuff that wouldn't go through the  
patch queue we'd want commits from the patch queue to be marked  
differently.

That brings up another idea for the patch management webapp...  
presumably it could handle most/all of the process of actually  
committing a patch. Granted, that's not a huge amount of work, but  
it's silly to have committers do by hand that hich could be automated.
--
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)