Re: Re: TODO-list on wiki (was: TODO update about SQLSTATE to PGconn) - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Re: TODO-list on wiki (was: TODO update about SQLSTATE to PGconn)
Date
Msg-id 200803121532.m2CFWGB28769@momjian.us
Whole thread Raw
In response to Re: Re: TODO-list on wiki (was: TODO update about SQLSTATE to PGconn)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: TODO-list on wiki (was: TODO update about SQLSTATE to PGconn)  ("Dave Page" <dpage@pgadmin.org>)
Re: Re: TODO-list on wiki (was: TODO update about SQLSTATE to PGconn)  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > Tom Lane wrote:
> >> Personally I think it would be just fine if we had only the wiki copy
> >> and forgot about shipping it in tarballs.
> 
> > The problem with not shipping the TODO file at all is that TODO gives
> > users a list of all known bugs/missing features in that major release. 
> 
> This seems to me to be nonsense.  You've never maintained the
> back-branch versions of the TODO list, so they're out of date anyway
> --- ie, they don't account for problems discovered post-release.

It is a best effort with our limited resources.

> In any case I've always thought that the TODO was developer-oriented
> documentation, not something users would read.  If there's a shortcoming
> in a feature, it ought to be documented in the SGML manual.

It typically isn't, except for major issues, again due to lack of
resources.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://postgres.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: count(*) performance improvement ideas
Next
From: Bruce Momjian
Date:
Subject: Re: count(*) performance improvement ideas