Re: Project scheduling issues (was Re: Per tuple overhead, cmin, cmax, OID)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Manfred Koizar <mkoi-pg(at)aon(dot)at>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Project scheduling issues (was Re: Per tuple overhead, cmin, cmax, OID)
Date: 2002-06-09 05:41:22
Message-ID: 3510.1023601282@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Marc G. Fournier" <scrappy(at)hub(dot)org> writes:
> I *really* wish ppl would stop harping on the length of the last beta
> cycle ... I will always rather delay a release due to an *known*
> outstanding bug, especially one that just needs a little bit more time to
> work out, then to release software "on time" ala Microsoft ...

I don't think that's at issue here. No one was suggesting that we'd
force an *end* to beta cycle because of schedule issues. We ship when
we're satisfied and not before. I'm saying that I want to try to
*start* the beta test period on-time, rather than letting the
almost-beta state drag on for months --- which we did in each of the
last two cycles. Development time is productive, and beta-test time
is productive, but we're-trying-to-start-beta time is not very
productive ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2002-06-09 10:38:26 Re: Roadmap for a Win32 port
Previous Message Marc G. Fournier 2002-06-09 05:32:22 Re: Project scheduling issues (was Re: Per tuple overhead,