Re: No Issue Tracker - Say it Ain't So!

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Robert Haas <robertmhaas(at)gmail(dot)com>, Catalin Iacob <iacobcatalin(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, YUriy Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: No Issue Tracker - Say it Ain't So!
Date: 2016-01-08 08:37:35
Message-ID: CABUevEx3t1NFpdwO6O2_GEB_8j_b8or73iw5BwWkXjS-s7Kn0A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 7, 2016 at 10:57 PM, Joshua D. Drake <jd(at)commandprompt(dot)com>
wrote:

> On 01/07/2016 12:32 PM, Jim Nasby wrote:
>
>> On 1/7/16 1:49 PM, Josh Berkus wrote:
>>
>>> Yeah, we could also get rid of this conversation:
>>>
>>> "Here's a patch for X, which is on the TODO list"
>>>
>>> "Oh, we've obsolesced that, that was added to the TODO before we had Y"
>>>
>>> ... by auto-closing TODO items at a certain age.
>>>
>>
>> Even if not auto-closed at least it'd be easy to find old items.
>>
>> Bonus points if we attract some volunteer project managers that will
>> keep tabs of all those kinds of things...
>>
>
> /me waves hand....
>
> There are quite a few contributing companies that likely have people that
> could help out with this in an educated fashion but aren't coders.

Sort of like how they could also have helped out with cf management?

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Konstantin Knizhnik 2016-01-08 08:58:12 Re: Optimizer questions
Previous Message Pavel Stehule 2016-01-08 08:30:41 PostgreSQL 9.5.0 regress tests fails with Python 3.5.0