| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | David Fetter <david(at)fetter(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Time to do our Triage for 9.4 |
| Date: | 2014-01-08 20:03:25 |
| Message-ID: | 52CDAF0D.20500@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> What about doing the triage the first two days or so of the CF? Then we
> know which patches have been submitted/updated and we haven't yet
> performed too many reviews of patches which aren't going to make it.
If we triage the patches we already have NOW, then it'll be possible to
triage the new/updated stuff which comes in in the first 48 hours of the
CF. If we wait until the CF begins, we'll spend at least the first week
of the CF triaging.
That's why we set this schedule at the developer meeting.
And besides, we already know what category *your* patch belongs in ...
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2014-01-08 20:27:51 | Re: Standalone synchronous master |
| Previous Message | Andres Freund | 2014-01-08 19:53:47 | Re: Time to do our Triage for 9.4 |