Date: Tue, 27 Apr 2004 13:49:22 -0400
From: Tim Conrad <tim@timconrad.org>
To: Josh Berkus <josh@agliodbs.com>
Cc: "Marc G. Fournier" <scrappy@postgresql.org>,
	PostgreSQL advocacy <pgsql-advocacy@postgresql.org>
Subject: Re: Upcoming Features WAS: What can we learn from MySQL?
Message-ID: <20040427174922.GA35932@external.timconrad.org>
References: <200404262213.44601.jm@poure.com>
	<20040427165746.GA1873@external.timconrad.org>
	<200404271030.28173.josh@agliodbs.com>
	<200404271039.52552.josh@agliodbs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200404271039.52552.josh@agliodbs.com>
User-Agent: Mutt/1.4.1i


On Tue, Apr 27, 2004 at 10:39:52AM -0700, Josh Berkus wrote:
> Tim, Folks:
> > I guess there's a perception that we are "above" the marketeering of MySQL
> > and Microsoft, where features are promised as much as 6 years before they
> > appear, or are heavily publicized while still in alpha.   So the most you'd
> > be likely to get the community to commit to is maintaining a list of
> > easy-to-read "Major Features in Development".
> 
> Actually, I really like this idea.  It could go like:
> 
> Feature				Lead			Status	
> Improved Memory Use		Jan Wieck		Complete, Committed for 7.5
> HA M-S Replication		Jan Wieck		Alpha testing
> PITR					Simon Riggs	Early Development
> Tablespaces			Gavin Sherry	Late Development
> Integrated pg_autovacuum	Matthew O'Con.	Planning
> Server Clustering		None			Developer Needed
> etc.
> 
> As well as giving the press something to look at, this would give programmers 
> and corporate sponsors an idea of where their time/money would be of use.  
> And it could put to bed the myth that we're not constantly improving.

This suggestion would be good. Something that's not super-detailed
and not super-technical. Also stuff that's on the 'todo' list that
is certianly long-range goals as well - just so people are aware
that it's something that the 'group' is aware of as well as a need.


Tim