On Mon, 10 Mar 2003, Tom Lane wrote:
> Justin Clift <justin@postgresql.org> writes:
> > The scenario that's appealing to me the most is this for the next release:
> > PostgreSQL 8.0
> > + Includes PITR and the Win32 port
>
> If the folks doing those things can get done in time, great. I'm even
> willing to push out the release schedule (now, not later) to make it
> more likely they can get done. What I'm not willing to do is define
> the release in terms of "it happens when these things are done". We
> learned the folly of that approach in 7.1 and 7.2. Setting a target
> date and sticking to it works *much* better.
The thing is, IMHO, everyone knew the release scheduale for v7.4, so if
they aren't ready now, I can't really see justifying pushing things back
in hopes that they will be ready then ...