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).
For those dismayed by the number of things caught just after release, let
me say that it's just human nature. There are lots of us who want to use
the product, but do not want to be swamped by the number of things wrong
with a "beta" release. Lots of people just won't try it out until it's
advertised as final. This is the reason why there is a gcc 2.7.2.2 for
example.
In other words the number of bugs reported now reflects the greater number
for people using the product. While the number of bugs is bad, the number
of users is good. Treat the users' bug reports with respect and they'll
stay around and be happy and the product will keep getting better and we'll
keep getting more users until WE TAKE OVER THE WORLD.
Oops, excuse me. I'm all better now, really. ;-)
Signature failed Preliminary Design Review.
Feasibility of a new signature is currently being evaluated.
h.b.hotz@jpl.nasa.gov, or hbhotz@oxy.edu
------------------------------
