Re: How do we track backpatches?

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: How do we track backpatches?
Date: 2013-06-18 02:48:02
Message-ID: 1371523682.13762.10.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2013-06-17 at 17:11 -0700, Josh Berkus wrote:
> Contributors,
>
> While going through this mailing list looking for missing 9.4 patches, I
> realized that we don't track backpatches (that is, fixes to prior
> versions) at all anywhere. Where backpatches are submitted by
> committers this isn't an issue, but we had a couple major ones (like the
> autovacuum fix) which were submitted by general contributors. The same
> goes for beta fixes.
>
> Should we add a "prior version" category to the CF to make sure these
> don't get dropped? Or do something else?

A separate commit fest for tracking proposed backpatches might be
useful.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2013-06-18 02:55:44 spurious wrap-around shutdown
Previous Message Peter Eisentraut 2013-06-18 02:45:07 Re: dynamic background workers