From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Julien Rouhaud <rjuju123(at)gmail(dot)com>, 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 13:27:43 |
Message-ID: | CAFBsxsHdAQwsc4wzW3+tPz4A9275aOqcse0G7q0fP_Bd-60V0A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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"?
--
John Naylor
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Konstantin Knizhnik | 2020-10-28 13:44:12 | cannot freeze committed xmax |
Previous Message | John Naylor | 2020-10-28 13:26:09 | Re: cutting down the TODO list thread |