Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 909229FBBEB for ; Wed, 2 May 2007 07:46:59 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 48838-07 for ; Wed, 2 May 2007 07:46:45 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id F35D99FBBE4 for ; Wed, 2 May 2007 07:46:48 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id l42Akk127514; Wed, 2 May 2007 06:46:46 -0400 (EDT) From: Bruce Momjian Message-Id: <200705021046.l42Akk127514@momjian.us> Subject: Re: Feature freeze progress report In-Reply-To: <200705012151.51915.josh@agliodbs.com> To: Josh Berkus Date: Wed, 2 May 2007 06:46:45 -0400 (EDT) CC: pgsql-hackers@postgresql.org X-Mailer: ELM [version 2.4ME+ PL123] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/102 X-Sequence-Number: 102704 Josh Berkus wrote: > Bruce, > > > As an example, how is patch information going to help us review HOT or > > group-item-index? There is frankly more information about these in the > > archives than someone could reasonable read. What someone needs is a > > summary of where we are now on the patches, and lots of time. > > The idea is to provide ways for other people to help where they can and to > provide better feedback to patch submitters so that they fix their own issues > faster. Also, lesser PostgreSQL hackers than you could take on reviewing the > "small" patches, leaving you to devote all of your attention to the "big" > patches. > > Actually, that can happen with the current system. The real blocker there is > that some people, particularly Tom, work so fast that there's no chance for a > new reviewer to tackle the easy stuff. Maybe the real solution is to > encourage some of our other contributors to get their feet wet with easy > patches so that they can help with the big ones later on? > > That is, if the problem is people and not tools, then what are we doing to > train up the people we need? We seem to handle trivial patches just fine. The current problem is that the remaining patches require domain or subsystem-specific knowledge to apply, e.g. XML or WAL, and those skills are available in a limited number of people. If I had the expertise in those areas, I would have applied the patches already. -- Bruce Momjian http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +