On Fri, 20 Jun 1997, Henry B. Hotz wrote:
> At 6:25 PM 6/20/97, Igor wrote:
> >Well...I will start working on Purifying Postgres this weekend....but all
> >this will have to go to 6.2 ... sll new features should go to 6.2.
> >Probably would be a good idea then to apply the most important patches
> >(like the endian patch) and let 6.1 go..I dunno...
>
> My $0.02 is that the Vadim's stuff goes into 6.2. The endian patch, Tom's
> fix for the datetime bug (BTW, Tom, you did take care of the msec/usec
> difference in Solaris, right?), and any Purification fixes go into 6.1.1
> (or whatever we call it).
This entails there will be two different development releases, which
there won't be.
Today is the 20th of June...~1 week after officially releasing v6.1.
So far as I've been able to see, nobody has thrown in anything that will
require a dump/reload to upgrade, and at this point, as that any of the
developers hold off on any patches *that will require a dump/reload*.
Between now and the 1st of July, everyone should be concentrating
on getting rid of as many of the bug reports as it is conceivably possible
to do. On the 1st, a new release, named v6.1p1 will be released, which will
make the end of the v6.1 development cycle, and begin v6.2, which will
most likely be in development for several months...
We've already done over a month of debugging/fixes for v6.1, and the
reports that have been coming in since the release *should* just be minor
changes.
Unless someone has this *major* showstopper bug that just *has* to be
fixed in v6.1p1, July 1st is pretty much a "set in concrete" sort of date...
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
------------------------------
