On Mon, 5 May 2003, Tom Lane wrote:
> ...
>
> If we're going to slip then we should establish a new release target
> date several months away (September or later), and hold to that schedule.
That's why I say try and get a realistic estimate and then a judgment can be
made as to whether the freeze stays or it slips _a little_.
> But is that really a better plan? We have accomplished quite a lot
> since last September, and holding those improvements out of the hands of
> users for months more is not a zero-cost thing. Nor do I take it as a
> sure thing that we won't be hearing the very same complaint come
> September. Both of these projects were supposed to have been done
> months ago, and they're not done. That gives me no confidence that
> they'll meet the next deadline we set. If September comes and we still
> have no working Win32 port, will you vote to delay again?
No, I wouldn't, but then I was thinking more of a month, two at the very most,
certainly not stretching it as far as Sept.
For a current client I actually prefer to get an early release, even June is
pushing it a bit. On the other hand if the release isn't going to be out in
time for me to switch to it for the first release of this project, which it may
well not be on the current release schedule, then I'd certainly like one with
PITR available to make upgrading attractive not just done for the sake of
upgrading.
--
Nigel J. Andrews
