From owner-freebsd-stable Sun Mar 15 11:41:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19530 for freebsd-stable-outgoing; Sun, 15 Mar 1998 11:41:30 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bsampley.vip.best.com (bsampley.vip.best.com [206.184.160.196]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19524 for ; Sun, 15 Mar 1998 11:41:19 -0800 (PST) (envelope-from bsampley@best.com) Received: from localhost (localhost [127.0.0.1]) by bsampley.vip.best.com (8.8.8/8.8.7) with SMTP id LAA04637 for ; Sun, 15 Mar 1998 11:39:48 -0800 (PST) (envelope-from bsampley@best.com) Date: Sun, 15 Mar 1998 11:39:11 -0800 (PST) From: Burton Sampley X-Sender: bsampley@bsampley.vip.best.com To: freebsd-stable@FreeBSD.ORG Subject: Re: Help! Upgrade 2.2.5-RELEASE to 2.2-STABLE. In-Reply-To: <350BA5A7.4B30A82E@dal.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- Greetings, I just want to throw in my 2 cents worth. I think it's a great idea to add a README file to /usr/src, but the biggest hiccup I see, is that adds yet another task for the already overburdened person submitting the code. Also, would a separate README be created for each major change? Who would be responsible for making sure that it is up to date at the exact second you decide to cvsup so you actually get the correct revision of the file? It's a good idea and I would love to have something like it in place, but since -stable is such a constantly moving target, I think it would create a significant burden on someone to try to maintain it. One solution I came up with is another person not actually involved in the coding monitoring the cvs-commit mailing list and then appropriately updating or creating the README. The biggest problem with this idea is miscommunication or the possibility of a big change slipping through the cracks. Another solution I thought of would be to create another mailing list like announce-stable where these types of heads-up announcements could be broadcast to the appropriate audience. Postings would be limited to people with commit authorization. The biggest problem with this idea is it does not give a clear mechanism for further discussion and follow-up questions. With the separate mailing list (which subscription to would be mandatory for subscribing to -stable) that would provide an easier mechanism to search the archives for missed pertinent postings. I don't know how easy this would be to create/maintain. - -burton- - --------------- Burton Sampley bsampley@best.com or bsampley@haywire.csuhayward.edu PGP key available at http://www.best.com/~bsampley/pgp.html -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNQwuZXt2O8KJtMdBAQHuVQQAoI0PJz+qgpX3TI3Lq3EUY7T1XHZ+/Mod J6ikl16Net0swUripJnaq7IrR2cSa6NjofQc5uXDdLSXa45U56eiWNo1fhx3vtpA 9DK2hcbUgovUIbx/PIoahVc+S5vs097tqGVWISDP5GnX6A9eEsZkEbTXOCHfeYSg K4+90/dpazE= =V2fT -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message