Skip site navigation (1) Skip section navigation (2)

Re: 8.5 development schedule

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: jd(at)commandprompt(dot)com
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: 8.5 development schedule
Date: 2009-07-01 21:38:41
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Joshua D. Drake wrote:
> On Wed, 2009-07-01 at 17:13 -0400, Tom Lane wrote:
> > "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> > > On Wed, 2009-07-01 at 17:01 -0400, Tom Lane wrote:
> > >> It comes down to somebody having the willingness to say "no" and the
> > >> authority to make it stick.  Robert mentioned upthread that the
> > >> committers don't want to be seen as throwing their weight around,
> > 
> > > Is that the purpose of core? To make exactly those decisions? 
> > 
> > Core has never seen itself as intended to make feature-by-feature
> > decisions.  People seem to be willing to defer to us on release
> > schedule-setting, but it's not clear to me that the community has
> > delegated us more authority than that.
> I would agree that having core decide on specific features is probably a
> stretch but having core set a cut date to which *all* patches that don't
> make that date? That seems within purview.

Define "make that date"?  That is the problem.

  Bruce Momjian  <bruce(at)momjian(dot)us>

  + If your life is a hard drive, Christ can be your backup. +

In response to


pgsql-hackers by date

Next:From: Andrew DunstanDate: 2009-07-01 21:42:03
Subject: Re: 8.5 development schedule
Previous:From: Joshua D. DrakeDate: 2009-07-01 21:18:49
Subject: Re: 8.5 development schedule

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group