Re: bug tracking system

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Nathan Wagner <nw+pg(at)hydaspes(dot)if(dot)org>
Cc: Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: bug tracking system
Date: 2019-02-06 02:02:20
Message-ID: 20190206020220.GA4015@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2019-Feb-03, Nathan Wagner wrote:

> If the bug seemed to be either an actual bug or something that would
> have actual work done, I marked these as open. It's entirely probable
> that some or most of these are actually fixed. There were a number
> of cases where committers emailed in a "will fix" type message, but
> I don't have any indication that this was actually done.

Yeah, this is pretty common and unhelpful. We should reply to the
mailing list with a commit ID or something.

> I have used the regex /Fixes bug #([0-9]+)/ to automatically look for
> commits purporting to fix bugs by number.

Let's use that.

> > ... and we probably want to
> > piggyback on our archives rather than having its own copy of the emails.
> I sort of do both. The pgbugs list is processed on my server via
> procmail and a perl script, so I have a copy of the emails, but
> the links for each email point back to the archives, rather than
> my copy.


Álvaro Herrera
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tsunakawa, Takayuki 2019-02-06 02:03:34 RE: speeding up planning with partitions
Previous Message Alvaro Herrera 2019-02-06 01:53:37 Re: Don't deform column-by-column in composite_to_json