Re: cutting down the TODO list thread

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: cutting down the TODO list thread
Date: 2020-10-28 14:35:15
Message-ID: CAOBaU_aU8mAGPms5p8jYUH6q9T00jzK0ZakFa9vGOf_Mfw79=A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 28, 2020 at 9:27 PM John Naylor
<john(dot)naylor(at)enterprisedb(dot)com> wrote:
>
> On Wed, Oct 28, 2020 at 6:52 AM Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>>
>> On Wed, Oct 28, 2020 at 11:15 AM Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
>> >
>> > On Wed, 28 Oct 2020, 17:55 Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de wrote:
>> >> I'm totally on board with cleaning the list up, but how about marking as "won't fix" (or similar) instead of actually removing the items? That should help to prevent the same exact items from appearing on the list again, which they eventually would, I believe.
>> >
>> >
>> > +1
>>
>> A small technical detail on the topic but if doing that, let's not
>> mark them as that inline -- create a separate page with those items on
>> it.
>
>
> How about a section on the same page at the bottom, near "features we don't want"?

Yes, that's what I was thinking, otherwise it'll still be too easy to miss.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniil Zakhlystov 2020-10-28 15:09:40 Re: libpq compression
Previous Message David G. Johnston 2020-10-28 14:21:09 Re: A new function to wait for the backend exit after termination