From owner-freebsd-questions  Mon Nov  2 04:24:35 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA02464
          for freebsd-questions-outgoing; Mon, 2 Nov 1998 04:24:35 -0800 (PST)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA02458
          for <questions@FreeBSD.ORG>; Mon, 2 Nov 1998 04:24:34 -0800 (PST)
          (envelope-from xroot@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id EAA02320;
	Mon, 2 Nov 1998 04:26:00 -0800 (PST)
Message-Id: <199811021226.EAA02320@implode.root.com>
To: cmascott@world.std.com (Carl Mascott)
cc: questions@FreeBSD.ORG
Subject: Re: Official maintenance policy for -stable? 
In-reply-to: Your message of "Mon, 02 Nov 1998 07:08:16 EST."
             <199811021208.AA06868@world.std.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Mon, 02 Nov 1998 04:26:00 -0800
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>What is the official policy about fixing bugs in -stable?

   The basic policy is that fixes must be committed to -current first and
then brought into -stable when it is felt that they have had adequate testing.
Sometimes this is immediate, but most of the time it is weeks, months, or
never. Serious bugfixes almost always make it into -stable, less serious
bugfixes are sometimes overlooked. The best way to get a fix into -stable is
to pester people about it. Otherwise it is up to the good memory of the
committer to remember it, with some amount of random chance added in.

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project

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