From owner-freebsd-doc@FreeBSD.ORG Wed Feb 17 20:49:19 2010 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 230E1106568D for ; Wed, 17 Feb 2010 20:49:19 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id E9D8D8FC16 for ; Wed, 17 Feb 2010 20:49:18 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 98B8246B0D; Wed, 17 Feb 2010 15:49:18 -0500 (EST) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id C9E838A024; Wed, 17 Feb 2010 15:49:17 -0500 (EST) From: John Baldwin To: freebsd-doc@freebsd.org Date: Wed, 17 Feb 2010 13:47:38 -0500 User-Agent: KMail/1.12.1 (FreeBSD/7.2-CBSD-20100120; KDE/4.3.1; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201002171347.38786.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 17 Feb 2010 15:49:17 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Jonathan Vasquez Subject: Re: Document improvement X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Feb 2010 20:49:19 -0000 On Sunday 14 February 2010 2:24:19 pm Jonathan Vasquez wrote: > URL: > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/version-guide/decision- points.html > > CURRENT: > "If you are not immediately planning on going into production, you are > willing to work through a certain number of problems, and a new major > release is upcoming within the next few months, you may wish to investigate > installing that branch to help the project to test it and stabilize it to > make it the best release possible in the medium to long term." > > QUESTION: What branch are you referring to? CURRENT? If so then you must add > the CURRENT tag to this sentence. > > IMPROVED: "If you are not immediately going into production, and you are > willing to work through a certain number of problems, then you may wish to > install the CURRENT branch. In doing so you can help the project test and > stabilize it and make the next release the best it can possibly be." I'm not sure which branch it is talking about actually. It probably is HEAD (which is what the next bullet point references), but to me it can make sense to start tracking stable prior to an X.Y release with the plan of adopting the X.Y release. -- John Baldwin