Re: Pruning the TODO list

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Pruning the TODO list
Date: 2012-06-21 14:25:45
Message-ID: CA+U5nMJ5TNEf+apqH=7ejM9=ovskHi6b1B3tQEm4A1SdSMRa=A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 21 June 2012 15:00, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
>> On 21 June 2012 08:30, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>>> Nonetheless, it would be a good idea to prune the TODO list regularly,
>>> such as after a release.  We used to do that a bit, not so much lately,
>>> perhaps.  But everyone is invited to contribute to that.
>
>> The idea is to remove contentious issues from the list, to avoid the
>> waste of time.
>
> The thing is, a lot of stuff gets punted to the TODO list *because*
> it's contentious, ie there's not consensus on what to do.  If there
> were consensus we might've just done it already.  I'm not sure we want
> to remove such entries, though perhaps somehow marking them as debatable
> would be a good thing.
>
> There may well be stuff on the list that is no longer very relevant in
> today's world, but somebody would have to go through it item by item
> to decide which ones those are.  I'm not volunteering.

<smiles> Understood

I'll have a play. Maybe I should just go with the idea of "Simon's
TODO List" - stuff I personally think is worth working on, and leave
it at that.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alex Hunsaker 2012-06-21 14:27:41 Re: pl/perl and utf-8 in sql_ascii databases
Previous Message Magnus Hagander 2012-06-21 14:19:31 Re: Release versioning inconsistency