From: | Don Baccus <dhogaza(at)pacifier(dot)com> |
---|---|
To: | Ned Lilly <ned(at)greatbridge(dot)com>, Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
Cc: | Ben Adida <ben(at)openforce(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, Peter Eisentraut <peter_e(at)gmx(dot)net>, "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, pgsql-hackers(at)hub(dot)org |
Subject: | Re: Bug tracking (was Re: +/- Inf for float8's) |
Date: | 2000-08-21 14:35:10 |
Message-ID: | 3.0.1.32.20000821073510.014e07c0@mail.pacifier.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>At 10:22 PM 8/20/00 -0400, Ned Lilly wrote:
>>If you all don't mind, I think it'd be great to keep this discussion on the
>>list. As some of you know, Great Bridge is working on its own project
>>hosting site (including a PG-backed bug tracking module). We're not quite
>>ready to pull back the curtain yet, but are getting close, and will be
>>actively soliciting input (and hacks) from the community.
Another implication which missed me first time 'round is that Great Bridge
might be planning to have its own bug reporting system, separate from
that used by the development community at large?
I hope not. There should be one central place for bug reporting. If
Great Bridge wants to run it, fine, also if Great Bridge wants to be able
to incorporate some sort of prioritization system for those with paid
support (or some other discriminatory system) it is still probably better
to figure out a way to accomodate it rather than have two separate
bug reporting systems.
- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
Nature photos, on-line guides, Pacific Northwest
Rare Bird Alert Service and other goodies at
http://donb.photo.net.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-08-21 14:37:29 | Re: Optimisation deficiency: currval('seq')-->seq scan, constant-->index scan |
Previous Message | Tom Lane | 2000-08-21 14:23:37 | Re: AW: pg_attribute growing and growing and growing |