Skip site navigation (1) Skip section navigation (2)

Re: How can I check the treatment of bug fixes?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, MauMau <maumau307(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: How can I check the treatment of bug fixes?
Date: 2011-05-27 18:19:25
Message-ID: 17404.1306520365@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Fri, May 27, 2011 at 12:21 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> That patch is waiting for a committer who knows something about Windows
>> to pick it up.

> It might be useful, in this situation, for the OP to add this patch to
> the CommitFest application.

> https://commitfest.postgresql.org/action/commitfest_view/open

> Also, I think it's about time we got ourselves some kind of bug
> tracker.

[ shrug... ]  I think the main problem is a lack of committer cycles.
If so, the extra bureaucracy involved in managing a bug tracker will
make things worse, not better.

However, if someone *else* wants to do the work of entering bugs into a
tracker and updating their status, far be it from me to stand in their
way.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2011-05-27 18:34:10
Subject: Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum
Previous:From: Tom LaneDate: 2011-05-27 18:13:46
Subject: pgsql: Improve corner cases in pg_ctl's newwait-for-postmaster-startup

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group