From: | Cédric Villemain <cedric(at)2ndquadrant(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com> |
Subject: | Re: How do we track backpatches? |
Date: | 2013-06-18 10:15:23 |
Message-ID: | 201306181215.27662.cedric@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Le mardi 18 juin 2013 04:48:02, Peter Eisentraut a écrit :
> 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.
Backpatches are bugs fix, isnt it ?
I will like to have a mail based bug tracker like debbugs.
--
Cédric Villemain +33 (0)6 20 30 22 52
http://2ndQuadrant.fr/
PostgreSQL: Support 24x7 - Développement, Expertise et Formation
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2013-06-18 10:32:42 | Re: How do we track backpatches? |
Previous Message | Szymon Guz | 2013-06-18 10:01:09 | Re: Add regression tests for SET xxx |