| From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: cutting down the TODO list thread |
| Date: | 2023-01-16 10:17:23 |
| Message-ID: | CAFBsxsEv1kkDih5D_nodrQguK6F5QfjcZBcL8qXuR54o58MApw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> We could also revise the developer FAQ:
> - remove phrase "Outstanding features are detailed in Todo."
> - add suggestion to to check the Todo or Not_worth_doing pages to see if
the desired feature is undesirable or problematic
> - rephrase "Working in isolation is not advisable because others might be
working on the same TODO item, or you might have misunderstood the TODO
item." so it doesn't mention 'TODO' at all.
There is also
https://wiki.postgresql.org/wiki/So,_you_want_to_be_a_developer%3F#TODOs
Changing the description of what links to the todo list will probably do
more to reduce confusion than language in the todo list itself.
--
John Naylor
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2023-01-16 10:23:24 | Re: Polyphase merge is obsolete |
| Previous Message | Peter Eisentraut | 2023-01-16 10:16:38 | Re: Add BufFileRead variants with short read and EOF detection |