From owner-freebsd-current Thu Jan 6 15:44:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 16AC1158EB; Thu, 6 Jan 2000 15:43:32 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA01121; Thu, 6 Jan 2000 15:48:26 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001062348.PAA01121@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: scanner@jurai.net Cc: "David O'Brien" , Darren Reed , committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th In-reply-to: Your message of "Thu, 06 Jan 2000 18:26:16 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Jan 2000 15:48:26 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > FreeBSD releases. So thats moot. The point im trying to make is regardless > of the state IPv6 is in, leaving it out of a major release is a no no IMO. If you believe this is really an issue, then you should be scolding the KAME folks and not the rest of us. They knew when the deadlines were, just like the rest of you. And in fact, if you cared at all about it, rather than waiting until _now_ and whining about it, you could have noticed that they were falling behind and offered to _help_ them with their work in order to make the deadling. > Now everyone is perfectly aware of the fact that -core tries to keep > releases and FreeBSD in general as stable as possible. Actually, -core don't do this at all. It's the responsibility of the entire developer team to do it, and it's one that many of you seem to enjoy shirking. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message