On Thu, 29 Apr 2004, Tom Lane wrote:
> "Marc G. Fournier" <scrappy@postgresql.org> writes:
> > *If* June 1st comes along, and Win32 isn't ready, there is nothing wrong
> > with freezing the code *except* for a pending Win32 patch ...
>
> Yeah there is ...
>
> In the first place it's unfair to other developers to make schedule
> slips at the last moment, and especially to *plan* to do so.
Isn't it equally unfair to slip the scheduale that developers that have
been working on some large features (PITR, 2PC immediately coming to mind)
have been working towards based on a deadline? If Win32 that much more
important then those other features?
> I would prefer we determine at least two weeks, preferably a month, in
> advance whether there is going to be a schedule change. I think it's
> entirely appropriate to decide now whether we are going to hold to June
> 1 feature freeze or slip it. That gives other people a chance to do
> useful work while we approach the deadline.
>
> In the second, any Win32 issues that remain unresolved as of June 1
> are likely to be major enough (in terms of code impact) that we can't
> realistically contemplate slipping in post-beta patches for them.
> The fallback position is going to have to be no (supported) Win32 port
> in 7.5, not "we'll fix this in beta".
Personally, I think there are alot of large features that ppl have been
hard at getting complete in time for June 1st that we should stick to it,
else we're going to end up with 'yet another release' delayed in hopes
that the outstanding bugs in Win32 will get fixed in a reasonable amount
of time ...
June 1st, let's do beta for 7.5 and then branch onto 8.0, with 8.0 key'd
to the Win32 Native port being finished ...
If that means 8.0 happens to be September 1st, so be it ...
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664