Date: Mon, 30 Apr 2007 14:59:51 +0200
From: Zdenek Kotala <Zdenek.Kotala@Sun.COM>
Subject: Re: Feature freeze progress report
In-reply-to: <4635D973.90106@postgresql.org>
To: Dave Page <dpage@postgresql.org>
Cc: Bruce Momjian <bruce@momjian.us>, Tom Lane <tgl@sss.pgh.pa.us>,
	Heikki Linnakangas <heikki@enterprisedb.com>,
	Simon Riggs <simon@2ndquadrant.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Message-id: <4635E847.30001@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <200704301129.l3UBTsl20011@momjian.us>
	<4635D973.90106@postgresql.org>
User-Agent: Thunderbird 1.5.0.8 (X11/20061204)

Dave Page wrote:

> 
> In my original message I described my thinking:
> 
> - Developer submits patch, with additional info through a web interface.
> 
> - The web interface formats an email containing the patch description,
> patch and any other info entered, assigns it a patch number, and
> forwards it to the patches list.
> 
> - Discussion ensues on list as per normal. The tracking system monitors
> the list and automatically attaches any posts to the patch that have the
> appropriate reference in the subject line.
> 
> - Community members and committers can review the entire discussion
> through the systems web interface. Updated patches could be submitted
> online.
> 
> - Committers log into the system when necessary to alter the status
> (committed, rejected, awaiting revision, under review etc), or the queue
> name (8.3, 8.4 etc). This could also be done automagically via email
> keywords from specific addresses.
> 
> You would no longer need to manually manage the queue, and the
> committers would simply need to tweak the status flag as required.
> 


You can look on Apache Derby project. I think everything what you 
mentioned there Derby project is using.

See http://db.apache.org/derby/

		Zdenek