public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Robert Treat <[email protected]>
Cc: [email protected]
Cc: David Fetter <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Joshua D. Drake <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: [email protected]
Subject: Re: Getting a move on for 8.2 beta
Date: Sat, 2 Sep 2006 12:17:19 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Robert Treat wrote:
> On Saturday 02 September 2006 07:14, David Fetter wrote:
> > On Fri, Sep 01, 2006 at 09:46:02PM -0400, Bruce Momjian wrote:
> > > Peter Eisentraut wrote:
> > > > Bruce Momjian wrote:
> > > > > It pulls my a mailbox file I use, and it does instant updates as
> > > > > soon as I change it. It is a URL. Why do people care where it
> > > > > is?
> > > >
> > > > The complaint has been that not enough people help with reviewing
> > > > patches. That would indicate that the problem is not location but
> > > > scalability. If everything has to go through your private
> > > > mailbox, then it's not a very obvious process to outsiders.
> > >
> > > Well, you can grab items from there and apply them. I will remove
> > > them from the mailbox when I see the commit.
> >
> > This, in essence, is the problem. You're using the first person
> > singular here, and it's become obvious that one person can't keep up
> > with this any more. The project, thanks in part to your hard work,
> > has grown past that stage.
> >
>
> AFAICT Bruce is not the bottleneck and our problem is not that multiple people
> are reviewing the same item and duplicating effort, so I think your making
> conclusions based not on the evidence but instead on a desired outcome.
>
> No offense, a whole lot of this thread seems to be positioned that way, but
> the real problem seems to be we do not have enough patch reviewers. ISTM the
> questions we should be asking are who can actually help out with patch review
Let me explain what I do. I subscribe to most PostgreSQL email lists.
I basically try to make sure every bug, patch, or idea is processed. If
it is a bug via user error, did they get correct information. If it is
valid PostgreSQL bug, was it fixed or added to the TODO list. If it was
a patch, was it applied or rejected. If it is a feature request, was it
added to the TODO list or rejected.
That's about it, folks. Not a lot of fancy magic. As other people take
up these items, my workload will be reduced. I do not take ownership of
any of these things. I merely jump on them when they are _not_ dealt
with by others.
What I am unclear about is how all of this traffic is going to be pushed
into a system that cleanly categorizes it so others can understand it.
It can be done, but what is the cost/benefit to it?
Perhaps if email could be pushed into the system, and somehow
categorized as bug, patch, or feature request, and somehow removed only
when it is dealt with. That is what I do now via my mailbox.
--
Bruce Momjian [email protected]
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
view thread (101+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Getting a move on for 8.2 beta
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox