Re: Feature freeze progress report - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Feature freeze progress report
Date
Msg-id 87d51lqpez.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: Feature freeze progress report  (Naz Gassiep <naz@mira.net>)
Responses Re: Feature freeze progress report  (Marc Munro <marc@bloodnok.com>)
List pgsql-hackers
"Naz Gassiep" <naz@mira.net> writes:

> Even if the patch inventory wasn't kept right up to date, this system
> could potentially help many regression issues or bugs to surface sooner,

I just don't understand what this would accomplish. People run regressions
before submitting anyways. They can't run them on all architectures but bugs
that only affect some architectures are uncommon.

This seems to be merely institutionalizing having a large backlog of patches
which survive for long periods of time. But even in that situation I don't see
what it buys us. Detecting bitrot isn't terribly helpful and it doesn't help
us actually deal with the bitrot once it's happened.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Naz Gassiep
Date:
Subject: Re: Feature freeze progress report
Next
From: Dave Page
Date:
Subject: Re: Feature freeze progress report