James Hawtin <[EMAIL PROTECTED]> writes:
> You could aways release 1.7 without cookies as 1.6.1
That won't happen because there's too much new code -- HTTP
keep-alive, hash tables, new HTML parser, SSL, NT and VMS directory
listing support, progress display improvements, etc.
> is there enough new stuff to justify it being a major release?
1.7 is not a new major release, it's a new *minor* release. 2.0 would
be a new major release.
To rehash the versioning theory: Given version A.B.C, incrementing A
is a new major release, incrementing B is a new minor release, and
incrementing C is a new patch level.
> So if you want to release 1.7 drop 1.6.1 I think...
I agree here. IMHO 1.7 is not that unstable to warrant a parallel
1.6.1 release.
