| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Catalin Iacob <iacobcatalin(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(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-07 20:32:36 |
| Message-ID: | 568ECB64.6060204@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2016-01-07 21:12:37 | Re: WIP: Covering + unique indexes. |
| Previous Message | Jim Nasby | 2016-01-07 20:30:06 | Interesting read on SCM upending software and hardware architecture |