| From: | Christopher Browne <cbbrowne(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL Mailing Lists <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Daniel Farina <daniel(at)heroku(dot)com> |
| Subject: | Re: Bug tracker tool we need |
| Date: | 2012-07-07 00:44:13 |
| Message-ID: | CAFNqd5UbF-MzkySzZ_i+VZ1CHuesrmVOFrfVcXCnOwCX=1CKBA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wonder if maybe the nearest step towards "better bug tracker" is a more
readily referenceable mail archive.
Clearly, one of our "frictions" is searching for relevant messages, so
improved mail archive == lowered friction, no?
There's a very particular use case; people keep rueing that indexes get cut
off on a monthly basis. That's doubtless not the only pain, but it keeps
getting mentioned, so solving it seems valuable.
Having a correlation between commits, commitfest entries, and associated
email seems like another valuable addition.
Perhaps there are more... I'm not yet poking at anything that would
suggest "email database", either.
A lot of the analysis would be more network-oriented; putting more of a
Prolog hat on, not so much tabular / relational ...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2012-07-07 01:33:27 | Re: Bug tracker tool we need |
| Previous Message | Peter Geoghegan | 2012-07-07 00:42:48 | Re: enhanced error fields |