From owner-freebsd-doc@FreeBSD.ORG Wed Dec 3 10:37:49 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1B5C16A4CE for ; Wed, 3 Dec 2003 10:37:49 -0800 (PST) Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU [128.205.32.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96FB044049 for ; Wed, 3 Dec 2003 10:37:48 -0800 (PST) (envelope-from kensmith@cse.Buffalo.EDU) Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1]) hB3Ibmus001437 for ; Wed, 3 Dec 2003 13:37:48 -0500 (EST) Received: (from kensmith@localhost) by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id hB3IblVP001436 for doc@FreeBSD.org; Wed, 3 Dec 2003 13:37:47 -0500 (EST) Date: Wed, 3 Dec 2003 13:37:47 -0500 From: Ken Smith To: doc@FreeBSD.org Message-ID: <20031203183747.GA1326@electra.cse.Buffalo.EDU> References: <20031203124353.GD82966@droso.net> <20031203133557.GA23226@electra.cse.Buffalo.EDU> <20031203150958.GC72102@droso.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031203150958.GC72102@droso.net> User-Agent: Mutt/1.4.1i Subject: Re: Documentation of major changes to the ports collection X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2003 18:37:49 -0000 On Wed, Dec 03, 2003 at 04:09:58PM +0100, Erwin Lansing wrote: > Although I'm all that happy about starting two new documents, I keep > running into problems with how to combine the best of both worlds > and perhaps the best would be both. One plaintext UPDATING-style where > all ports-committers can add items for developers to and one relnotes-style, > which rotates at each release and is published at the website more oriented > at users. You're thinking about only two? ;-) Thoughts on having a third special one that is much more visible that lists security fixes? Speaking with my day job hat on I'm not *real* interested in constantly updating ports on lots of machines, I tend to do it at OS release times. But I'm much more interested in knowing when security issues in ports get addressed, for example the recent screen(1) issue. Sorry, just a thought. :-( -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |