On Fri, 10 Dec 1999, The Hermit Hacker wrote:
> Here's a question...should we beta on Feb 1st but make it 7.0? If we are
> going to be looking for a "long slog" for 7, why not "freeze" things on
> Feb 1st as v7, and start working on v8 with WAL, long tuples, etc, etc...
>
> Like, what point do we call things a major release? In a sense, MVCC
> probably should have been considered a large enough overhaul to warrant
> 7.0, no?
I thought Marc decided[1] last year to drop the minor.minor version
numbers. IOW, there would be no 6.6.1, 6.6.2, etc. Make the upcoming
release 7.0 and take care of any minor glitches in it as 7.1, 7.2 and
when WAL and the other stuff is ready - or as it's ready - release 8.0
and fix any glitches as 8.1, etc. Currently every minor release is really
a major one, so why not just mark it as such and not worry about it?
Vince.
[1] Or did you do that on inn-workers and not here? It was about the same
time FreeBSD dropped the major.minor.minor for the major.minor numbering.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include <std/disclaimers.h> Have you
seenhttp://www.pop4.net? Online Campground Directory http://www.camping-usa.com Online Giftshop
Superstore http://www.cloudninegifts.com
==========================================================================
