| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: How do we track backpatches? |
| Date: | 2013-06-19 18:55:25 |
| Message-ID: | CABUevEzNJsyx_GP4QHh08bw2FGpAFF4eWp59P-UYKN4BopHUqg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 19, 2013 at 8:54 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Josh Berkus wrote:
>>
>> > I'd imagine having a "CF" entry per release, so after a set of minor
>> > releases, the "CF" is closed.
>>
>> How would we name these?
>>
>> Also, what about patches for beta? Should we have a "beta" CF?
>
> Don't we have the Open Items wiki page for those? Seems to work well
> enough.
Yes. The CF app only tracks things that already have patches. For the
beta, we really need to track things that may not have been fixed - or
that may have been done, just only partially so far.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2013-06-19 18:55:42 | Re: Change authentication error message (patch) |
| Previous Message | Alvaro Herrera | 2013-06-19 18:54:27 | Re: How do we track backpatches? |