| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, 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 19:49:28 |
| Message-ID: | 568EC148.5080405@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 01/07/2016 10:30 AM, Jeff Janes wrote:
> I don't completely agree with that. I have often wanted to know when
> a specific item was added to the TODO page, and/or its individual edit
> history. With only a unified history of the entire TODO page, and
> with no wiki equivalent of "git blame", figuring this out is extremely
> tedious. A tracker would precisely solve this problem, if nothing
> else. And when I edit the wiki and forget to make a coherent edit
> summary, there is no way to fix that, while presumably an issue
> tracker would be more tolerant of people's imperfections.
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.
--
Josh Berkus
Red Hat OSAS
(opinions are my own)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-01-07 20:04:05 | Re: [COMMITTERS] pgsql: Windows: Make pg_ctl reliably detect service status |
| Previous Message | Konstantin Knizhnik | 2016-01-07 19:43:21 | Re: Optimizer questions |