| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Commit fest queue |
| Date: | 2008-04-09 18:05:56 |
| Message-ID: | 23970.1207764356@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> What would move us in the direction of this mythical "patch tracker" would be
> if we knew exactly what our workflow was. Once we know what our workflow is
> then we could pick a tool which enforces that workflow.
Well, I don't think we want or need an "enforced" workflow. What we
need is just a list of pending patches so that nothing falls through the
cracks. As you say, most of the work is in recognizing which emails
deserve to be entered into the list, and that's not subject to
automation (not in this decade anyway).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2008-04-09 18:09:34 | Re: Free Space Map data structure |
| Previous Message | Gregory Stark | 2008-04-09 17:45:09 | Re: Commit fest queue |