| From: | "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Kim Bisgaard <kim+pg(at)alleroedderne(dot)adsl(dot)dk>, Greg Stark <gsstark(at)mit(dot)edu>, Joe Abbate <jma(at)freedomcircle(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Getting a bug tracker for the Postgres project |
| Date: | 2011-05-31 15:04:28 |
| Message-ID: | 20110531150428.GE8700@staff-mud-56-27.rice.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 31, 2011 at 09:36:00AM -0400, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > On 05/31/2011 06:41 AM, Magnus Hagander wrote:
> >> We already have a search system that works reasonably well for the archives...
>
> > I trust this weas a piece of sarcasm. I spoke to more than a few people
> > at pgcon and nobody had a good word to say about the search system on
> > the archives.
>
> Please note, though, that there is no bug tracker anywhere whose search
> mechanism doesn't suck as much or more. If you're unhappy with the
> search stuff the solution is to improve it, not bring in another bad
> mechanism.
>
+1
Ken
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-05-31 15:13:13 | Re: Getting a bug tracker for the Postgres project |
| Previous Message | Kevin Grittner | 2011-05-31 15:02:49 | Re: Getting a bug tracker for the Postgres project |