From owner-svn-src-all@FreeBSD.ORG  Sat Apr 21 19:13:20 2012
Return-Path: <owner-svn-src-all@FreeBSD.ORG>
Delivered-To: svn-src-all@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 1033)
	id 328A1106566B; Sat, 21 Apr 2012 19:13:20 +0000 (UTC)
Date: Sat, 21 Apr 2012 19:13:20 +0000
From: Alexey Dokuchaev <danfe@FreeBSD.org>
To: Brooks Davis <brooks@freebsd.org>
Message-ID: <20120421191320.GA57272@FreeBSD.org>
References: <201204202137.q3KLbhNj056524@svn.freebsd.org>
	<CAFMmRNy6Ew_A1+CAq5Off+NxYxEMBHs8ZgfyG7pvVbbR9sCk7Q@mail.gmail.com>
	<20120421171128.GA6732@lor.one-eyed-alien.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
In-Reply-To: <20120421171128.GA6732@lor.one-eyed-alien.net>
User-Agent: Mutt/1.4.2.1i
Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org,
	src-committers@freebsd.org, Ryan Stone <rysto32@gmail.com>
Subject: Re: svn commit: r234504 - in head/sys: amd64/conf i386/conf
X-BeenThere: svn-src-all@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SVN commit messages for the entire src tree \(except for &quot;
	user&quot; and &quot; projects&quot; \)" <svn-src-all.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/svn-src-all>,
	<mailto:svn-src-all-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/svn-src-all>
List-Post: <mailto:svn-src-all@freebsd.org>
List-Help: <mailto:svn-src-all-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-src-all>,
	<mailto:svn-src-all-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Apr 2012 19:13:20 -0000

On Sat, Apr 21, 2012 at 12:11:28PM -0500, Brooks Davis wrote:
> On Sat, Apr 21, 2012 at 09:45:57AM -0400, Ryan Stone wrote:
> > Excellent!  Thanks to everybody who helped make this happen, starting
> > with the participants at dtrace.conf who gave us the requisite whacks
> > with the clue-by-four.
> > 
> > However, what is our policy for enabling features in -STABLE that are
> > known to be unstable?  If we MFC this I don't have the slightest worry
> > that somebody might see instability in their system just because the
> > hooks are all of a sudden there, but I would worry that somebody make
> > take DTrace hooks being enabled in GENERIC on -STABLE to imply that
> > DTrace is stable, start using it and being upset when they trip over a
> > DTrace bug.
> 
> I think we should note that it remains experimental and somewhat buggy
> in the release notes and probably in the MFC message.  Otherwise, it's
> like any new feature.  If you start using a feature in production
> without extensive testing you may be surprised.

I think that given we're just broken 9.x ice, it should be MFCed.

./danfe