From owner-freebsd-hackers Tue Dec 20 17:25:51 1994 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id RAA06336 for hackers-outgoing; Tue, 20 Dec 1994 17:25:51 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id BAA06305 for ; Wed, 21 Dec 1994 01:25:41 GMT Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id XAA10940; Sun, 18 Dec 1994 23:55:54 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.9/8.6.5) with SMTP id XAA00173; Sun, 18 Dec 1994 23:55:53 -0800 Message-Id: <199412190755.XAA00173@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: Stephen McKay cc: hackers@freebsd.org Subject: Re: Don't scream.. In-reply-to: Your message of "Mon, 19 Dec 94 16:45:55 +1000." <199412190645.QAA21561@orion.devetir.qld.gov.au> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 18 Dec 1994 23:55:52 -0800 Sender: hackers-owner@freebsd.org Precedence: bulk >Being a non-optimist I am surprised that a 2.0.5 based on -current is being >considered. I would expect that a 2.0.1 (note the small minor revision >implying only tiny changes) would be rolled consisting of 2.0 plus only We refered to 2.0-Alpha as 2.0.1 and 2.0-Beta as 2.0.2...so the best we could do would be a 2.0.3...but this might imply 2.0-Release, so perhaps 2.0.4. Since we *are* going to snapshot -current (there really is no other choice - some of the fixes are too extensive to back-port to 2.0R), and since this release will be halfway between 2.0 and 2.1, I think 2.0.5 is appropriate. >A number of things have already changed to make my 2.0 network binaries >not work with the -current kernel. What does this have to do with anything? The 2.0.5 network binaries work with a 2.0.5 kernel, and 2.0.5 will be a complete release...so what's the problem? >I realise that I may be too late in this instance, but you can take it as >read for next time! Actually, it's still not certain if 2.0.5 will happen at all...but if it is possible, I'm certainly behind it. -DG