From owner-freebsd-security Thu Jun 27 10:15:18 2002 Delivered-To: freebsd-security@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id D0A0537B400 for ; Thu, 27 Jun 2002 10:15:13 -0700 (PDT) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.4/8.12.4) with SMTP id g5RHF4bM009686; Thu, 27 Jun 2002 13:15:04 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 27 Jun 2002 13:15:03 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Matthew Dillon Cc: Stefano Riva , Mark.Andrews@isc.org, Brett Glass , security@FreeBSD.ORG Subject: Re: FreeBSD Security Advisory FreeBSD-SA-02:28.resolv In-Reply-To: <200206271658.g5RGweBm068044@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 27 Jun 2002, Matthew Dillon wrote: > I'm beginning to think that once all this settles down a 4.6.1 release > may be a good idea. Apache, ssh, now the resolver... nasty. I've been wondering about that also. However, the release engineering process is fairly heavy-weight, and the last time we did a light-weight x.x.1 release, people leapt on that opportunity to over-load it with lots of minor fixes that ended up making it a fairly broken release (since inevitably they weren't minor, but we weren't willing to do a full heavy-weight release). Regardless, we'd want to wait to spin a .x.x.1 release until the new OpenSSH was merged back, I think, so it will be a bit yet before we can really make a decision on this. The best strategy would be to literally slap down another tag on RELENG_4_6 and call it RELENG_4_6_1 point-release. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message