From owner-freebsd-security  Tue Oct  3 18:52:12 2000
Delivered-To: freebsd-security@freebsd.org
Received: from hub.lovett.com (hub.lovett.com [216.60.121.161])
	by hub.freebsd.org (Postfix) with ESMTP
	id 001C337B502; Tue,  3 Oct 2000 18:52:03 -0700 (PDT)
Received: from ade by hub.lovett.com with local (Exim 3.16 #1)
	id 13gdiy-00014I-00; Tue, 03 Oct 2000 20:52:00 -0500
Date: Tue, 3 Oct 2000 20:51:59 -0500
From: Ade Lovett <ade@FreeBSD.org>
To: Alfred Perlstein <bright@wintelcom.net>
Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org,
	freebsd-security@FreeBSD.org
Subject: Re: How long for -stable [ Re: cvs commit: src/usr.bin/finger finger.c ]
Message-ID: <20001003205159.A20891@FreeBSD.org>
References: <paul@originative.co.uk> <84222.970618959@winston.osd.bsdi.com> <20001003174313.U27736@fw.wintelcom.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001003174313.U27736@fw.wintelcom.net>; from bright@wintelcom.net on Tue, Oct 03, 2000 at 05:43:13PM -0700
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

[cc's trimmed a little]

On Tue, Oct 03, 2000 at 05:43:13PM -0700, Alfred Perlstein wrote:
> Might I suggest it'd be pretty helpful to have a couple of speedy
> 3.x (and probably 4.x) boxes set up some place with console access
> to make these types of fixes easier for our developers lacking in
> hardware resources.

What about ports?  How do you propose that they be tested, as opposed
to "it-compiles-so-ship-it" on these 3.x boxes if, say, the developer
in question only runs 4.x boxes, with a single not-yet-built 5.x box
for when 5.x settles down?

Or can we stick with the current ports policy of tracking -stable
and -current only, with a good luck to everyone else?  And what does
this policy mean anyway when we have two -stables, with the package
building cluster building for three environments?

-aDe

-- 
Ade Lovett, Austin, TX.			ade@FreeBSD.org
FreeBSD: The Power to Serve		http://www.FreeBSD.org/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message