Re: Commitfest status

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Commitfest status
Date: 2008-03-07 16:01:29
Message-ID: 200803071601.m27G1Te29041@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Tom Lane wrote:
>
> > > Right at the moment the raw data is still in Bruce's patch queue.
> > > It's becoming increasingly obvious that that isn't going to work;
> > > we can't have one man being a complete bottleneck for the entire
> > > process. I concur with your other suggestion to try to move to
> > > a wiki-based patch list, though it's unclear to me just how we
> > > should manage that. I think I'd prefer a small number of people
> > > (but more than just Bruce) responsible for updating the queue.
> >
> > Consider I am collecting all our open items from the past 10 months.
> > Even when I am done the patch queue is going to be a load of work ---
> > take a look at what is there now.
>
> We need storage of patches _outside_ our current patch queue.
>
> As a first problem with the statu quo, it's not possible for other
> people to add patches to the queue. Bruce suggests having a special
> email address that will allow people to bounce patches to. I see this
> as a kludge (a workable one perhaps, but still a kludge). Also it's not
> clear how it deals with authorization, though this is probably not a
> problem these days.

Right.

> The second problem is that there's no way to actually extract the patch
> from the queue. Cut'n pasting doesn't work, because whitespace is
> mangled. So one has to resort (retort?) to extracting the patch from
> one own's mbox, which sort of works -- unless it doesn't. And then you
> have to work out what's the email containing the latest patch is; if
> Bruce added a copy to the queue but the author updated it, how do you
> find that out?

Does the web site mhonarc archive have the same problem? Do you have
URLs? (You can download an mbox of my patches list from the top link.)

> As a stopgap measure, a Wiki page could work. Patches should be
> attached to the page, or a link to external storage should be posted
> (but not to archives, obviously).

The bottom line is that this going to be painful no matter how we go at
it:

http://momjian.us/cgi-bin/pgpatches

There are nine pages now. The patch queue will be twice that size once
I am done. I am trying to trim but it is difficult.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2008-03-07 16:10:41 Re: minimal update
Previous Message Teodor Sigaev 2008-03-07 15:56:37 Re: Behaviour of to_tsquery(stopwords only)