-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thus spake Matthias Scheler ("MS> ") sometime Today...

MS> In article <20040917235216.137F02AC7A@beowulf.gw.com>,
MS> 	christos@zoulas.com (Christos Zoulas) writes:
MS> >| >That's what I thought too, and 2.99 was luke's proposal IIRC. Can't we just
MS> >| >agree on that and move forward?
MS>
MS> Please.

I see the push for advancing major numbers as totally arbitrary and bogus.
The proposal as given makes no sense to me.

Why not, since we're at 2.x now, stick with 2.x until such time as we have
something so significantly different it can be called 3.x, proceeding along
the lines of 2.0, 2.1, 2.2, 2.3, etc. as we have historically done?

[I know, I should read the archives, and I shall, but still, preparing
 that well in advance to jump from 2.0 (stable) to 2.99 (development) to
 3.0 (stable) just seems wrong to me.  If this is the case, we need not
 have minor version numbering after the major version except to indicate a
 development release, i.e. we just have "NetBSD-2", "NetBSD-3", and so
 forth.  I'm not sure why this feels wrong, and it's just my opinion on
 something noteworthy enough to comment on but not enough to vehemently
 protest.]

MS> >| Does that mean 2.99A, 2.99B, 2.99C, .... 3.0?
MS> >| Or 2.99.1, 2.99.2, ... 3.0?
MS> >| Or 2.99, 2.991, 2.992, ... 3.0?
MS> [...]
MS> > The first has the advantage that it makes it clear that this is not a release
MS> > because the scheme is different, and the second has the advantage that it is
MS> > not different from the release scheme :-)
MS>
MS> The second scheme will work fine with the existing version number handling
MS> in "xsrc", the second one won't. That's not difficult fix but will require
MS> considerations for backwards compatibility e.g. how to get the same
MS> version number for 1.6Y (1.6.25) that we've used before.

You just contradicted yourself up there...("the second scheme will...
the second one won't."), so I'm a bit confused :)


				--*greywolf;
- --
Microsoft:
	"Just click on the START button and your journey to the Dark Side
	 will be complete!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFBUf6ODOGizqAnVRERAo5iAJ4va+/oUuNbkJNS/0ALcoaKx8Gq5QCfXdLj
oAIs4F41OUyP3QasfPylV2M=
=+ryR
-----END PGP SIGNATURE-----