Re: How do we track backpatches?
От | Noah Misch |
---|---|
Тема | Re: How do we track backpatches? |
Дата | |
Msg-id | 20130619041204.GA639791@tornado.leadboat.com обсуждение исходный текст |
Ответ на | Re: How do we track backpatches? (Peter Eisentraut <peter_e@gmx.net>) |
Список | 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
В списке pgsql-hackers по дате отправления: