From: | Brendan Jurd <direvus(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Getting a bug tracker for the Postgres project |
Date: | 2011-05-29 04:35:17 |
Message-ID: | BANLkTikhLCR0qEXpmhgFnASTedBMXNFSQQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 29 May 2011 14:04, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Anything that even pretends to be a bug tracker will do that. The
> real question is, who is going to keep it up to date? GSM has the
> right point of view here: we need at least a couple of people who
> are willing to invest substantial amounts of time, or it's not going
> to go anywhere. Seeing that we can barely manage to keep the mailing
> list moderator positions staffed, I'm not hopeful.
>
Well the good news is that first-pass triage of bug reports can be
done by pretty much anybody who is a moderately experienced postgres
user; they don't even need to be a hacker. They just need to know
when to send back a RTFM link, when to say "you didn't tell us your PG
version" / "post your query" / "post your explain analyse" / "post
your show all", and when to kick the bug report up to a sage hacker.
It's not glamorous work, but it is a very accessible way to
contribute, without the need to block out hours at a time. A bug
wrangler could very readily log in, sort out reports for 20 minutes
and then go do something else with the rest of their day.
Cheers,
BJ
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-05-29 05:10:48 | Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum |
Previous Message | Robert Haas | 2011-05-29 04:10:03 | Re: Getting a bug tracker for the Postgres project |