Re: Patch queue -> wiki

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Bruce Momjian" <bruce(at)momjian(dot)us>
Cc: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Greg Smith" <gsmith(at)gregsmith(dot)com>, "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch queue -> wiki
Date: 2008-04-05 01:49:26
Message-ID: 87abk9dqah.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-www


"Bruce Momjian" <bruce(at)momjian(dot)us> writes:

> Basically a Wiki takes 10x more time for me to modify something, so
> unless I get another 9 people to do the same amount of work I do on
> tracking, we are going to fall behind. I am not willing to increase the
> amount of time I already spend doing this. Perhaps distributed over the
> community there will be 9x more time spent on tracking, but I doubt it.

On a busy day we might get 5 patches submitted or updated. That's five lines
of text to add or edit. The hard part is reading the email and figuring out
what status the patch is in. Not coincidentally the lack of that info is also
why your list isn't very helpful.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2008-04-05 01:53:56 Re: modules
Previous Message Bruce Momjian 2008-04-05 01:46:05 Re: Re: [COMMITTERS] pgsql: Implement current_query(), that shows the currently executing

Browse pgsql-www by date

  From Date Subject
Next Message Tom Lane 2008-04-05 02:19:47 Re: Patch queue -> wiki
Previous Message Bruce Momjian 2008-04-05 01:14:06 Re: Patch queue -> wiki