public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tim Conrad <[email protected]>
To: Josh Berkus <[email protected]>
Cc: Marc G. Fournier <[email protected]>
Cc: PostgreSQL advocacy <[email protected]>
Subject: Re: Upcoming Features WAS: What can we learn from MySQL?
Date: Tue, 27 Apr 2004 13:49:22 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>



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

view thread (144+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Upcoming Features WAS: What can we learn from MySQL?
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox