Date: Tue, 27 Apr 2004 13:42:52 -0300 (ADT)
From: "Marc G. Fournier" <scrappy@postgresql.org>
To: Tim Conrad <tim@timconrad.org>
Cc: "Marc G. Fournier" <scrappy@postgresql.org>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>,
	PostgreSQL advocacy <pgsql-advocacy@postgresql.org>
Subject: Re: [HACKERS] What can we learn from MySQL?
In-Reply-To: <20040427161246.GB67934@external.timconrad.org>
Message-ID: <20040427134215.I60328@ganymede.hub.org>
References: <200404262213.44601.jm@poure.com>
	<200404262041.i3QKfZs28845@candle.pha.pa.us>
	<20040427152753.GA34713@external.timconrad.org>
	<20040427124336.R60328@ganymede.hub.org>
	<20040427161246.GB67934@external.timconrad.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 27 Apr 2004, Tim Conrad wrote:

> On Tue, Apr 27, 2004 at 12:58:59PM -0300, Marc G. Fournier wrote:
> > On Tue, 27 Apr 2004, Tim Conrad wrote:
> >
> > > 2) There doesn't seem to be a clear roadmap on Postgres features.
> > >    When certian things are expected. There's the TODO list that
> > >    Bruce maintains, but it only outlines 'near' fixes. MySQL has a
> > >    nice listing of what to expect in certian future versions.
> >
> > Not possible for us, since we have no "upper management" that dictates
> > what features get added, for when ...
>
> Not entirely true. I've read enough on the lists to see Bruce or
> others saying 'x feature isn't expected until version y.z'. Heck, to
> me, something that says 'we're hoping for feature x in version y.z',
> but it's not an exact science.  See the MySQL releases as an example
> :)

Ah, then in that case, look at the TODO list, pull out all items that have
a name beside them, and for those, they aren't expected until the next
version .. :)


----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org           Yahoo!: yscrappy              ICQ: 7615664