Re: No Issue Tracker - Say it Ain't So! - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: No Issue Tracker - Say it Ain't So!
Date
Msg-id 568ECB64.6060204@BlueTreble.com
Whole thread Raw
In response to Re: No Issue Tracker - Say it Ain't So!  (Josh Berkus <josh@agliodbs.com>)
Responses Re: No Issue Tracker - Say it Ain't So!  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
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...
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Interesting read on SCM upending software and hardware architecture
Next
From: David Rowley
Date:
Subject: Re: WIP: Covering + unique indexes.