| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: How do we track backpatches? |
| Date: | 2013-06-19 04:12:04 |
| Message-ID: | 20130619041204.GA639791@tornado.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 18, 2013 at 10:44:53PM -0400, Peter Eisentraut wrote:
> On Tue, 2013-06-18 at 12:32 +0200, Magnus Hagander wrote:
> > The CF app was and is specifically for dealing with CFs. Having it
> > deal with backpatches makes it, well, a bugtracker. It's not meant to
> > be that. If we want a bugtracker, then it has very different
> > requirements.
>
> It's not in evidence that the requirements are different. The CF app is
> basically a list of lists of patches with date information and
> associated person's names. Tracking backpatch candidates doesn't sound
> that much different. (That said, I'm not convinced backpatches need any
> tracking at all, but if they did, I think the CF app would be just
> fine.)
Agreed; bug fixes to be back-patched have appeared in most CFs, and I think
the CF process and app have served them fine.
--
Noah Misch
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hitoshi Harada | 2013-06-19 05:57:02 | Re: Patch for removng unused targets |
| Previous Message | Fabrízio de Royes Mello | 2013-06-19 03:45:36 | Re: Patch to add support of "IF NOT EXISTS" to others "CREATE" statements |