From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Call for 7.5 feature completion |
Date: | 2004-04-30 04:45:10 |
Message-ID: | 200404300445.i3U4jAb05817@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Marc G. Fournier wrote:
> On Fri, 30 Apr 2004, Bruce Momjian wrote:
>
> > Marc G. Fournier wrote:
> > > On Thu, 29 Apr 2004, Tom Lane wrote:
> > >
> > > > I guess my point is really "do you want to freeze on June 1 if *none* of
> > > > these features are done?"
> > >
> > > No, I agree that that would be foolish ... but there has also been alot
> > > done on the code over the past few months that even *one* of those
> > > features should be enough to put it over the top ...
> >
> > But we should have at least one done before setting a freeze date, and
> > the freeze date should be one month in the future. Right now we have
> > none.
>
> Now, that logic *doesn't* follow ... freeze date == that one feature makes
> more sense ... or freeze date == one month from May 1st *or* one feature,
> whichever is longer makes sense ...
But we don't want to have all our developers controlled by one feature
being completed. It isn't fair. They should get a good warning about
freeze starting.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-04-30 04:52:10 | Re: Current CVS tip segfaulting |
Previous Message | Matthew T. O'Connor | 2004-04-30 04:31:45 | Re: Call for 7.5 feature completion |