| From: | Devrim GÜNDÜZ <devrim(at)CommandPrompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Joshua D(dot) Drake" <jd(at)CommandPrompt(dot)com>, Dave Page <dpage(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 8.3 Release Schedule |
| Date: | 2007-07-19 21:11:00 |
| Message-ID: | 1184879460.2990.22.camel@laptop.gunduz.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Thu, 2007-07-19 at 16:47 -0400, Tom Lane wrote:
> As already noted, when we set the schedule we were not expecting to
> have so many large patches dropped on us at the very end of the devel
> cycle. What I'd like to think about is how can we avoid *that*
> happening again?
I think we can set a "Feature proposal" deadline, which is 2-3 months
before "feature freeze" deadline... If someone pushes the proposal and
it is accepted, he/she can begin coding until feature freeze...
Regards,
--
Devrim GÜNDÜZ
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-07-19 22:38:20 | Re: 8.3 Release Schedule |
| Previous Message | Tom Lane | 2007-07-19 20:47:05 | Re: 8.3 Release Schedule |