Re: Commitfest wrapup - Mailing list pgsql-hackers

From Jonathan S. Katz
Subject Re: Commitfest wrapup
Date
Msg-id 43b1c6cf-af15-d1b4-a975-28ad25fde868@postgresql.org
Whole thread Raw
In response to Re: Commitfest wrapup  (Greg Stark <stark@mit.edu>)
List pgsql-hackers
On 4/9/22 1:14 PM, Greg Stark wrote:
> On Sat, 9 Apr 2022 at 10:51, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>
>>> Sound like bugfixes to be backpatched.
>>
>> Yeah.  I'm not sure why these have received so little love.
> 
> Since bug fixes are important enough that they'll definitely get done
> (and can happen after feature freeze) there's a bit of a perverse
> incentive to focus on other things...
> 
> "Everybody was sure that Somebody would do it. Anybody could have done
> it, but Nobody did it"
> 
> I think every project struggles with bugs that sit in bug tracking
> systems indefinitely. The Open Issues is the biggest hammer we have.
> Maybe we should be tracking "Open Issues" from earlier in the process
> -- things that we think we shouldn't do a release without addressing.

The RMT does both delineate and track open issues as a result of new 
features committed and a subset of issues in existing releases. 
Traditionally the RMT is more hands off on the latter unless it 
determines that not fixing the issue would have stability or other 
consequences if it's not included in the release.

Jonathan



Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: failures in t/031_recovery_conflict.pl on CI
Next
From: Andres Freund
Date:
Subject: Re: Is RecoveryConflictInterrupt() entirely safe in a signal handler?