Re: Feature freeze progress report

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Feature freeze progress report
Date: 2007-05-01 20:10:07
Message-ID: 46379E9F.2030608@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-www

Josh Berkus wrote:
> If many people are going to block on using a web tool for submitting new
> versions of a patch, claiming responsibility for review, etc., though, then
> we should probably abandon this discussion right here. No new tool is going
> to work if we have people who won't make any changes at all in their work
> habits.
>

We could do most of what people want using a tracker, but that
discussion always seems to end up nowhere. And, as I have noted before,
use of a tracker will become a total mess unless there are adequate
resources to keep it clean and up to date (e.g. to put links in items to
mailing list discussions, update state etc.) So if the commercial
backers of PostgreSQL want better management of the project, maybe they
need to find some resources to help out.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stefan Kaltenbrunner 2007-05-01 20:10:56 Re: Fwd: [PATCHES] Preliminary GSSAPI Patches
Previous Message Magnus Hagander 2007-05-01 20:07:47 Re: Fwd: [PATCHES] Preliminary GSSAPI Patches

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2007-05-01 20:23:07 Re: Feature freeze progress report
Previous Message Simon Riggs 2007-05-01 18:09:50 Re: Feature freeze progress report