From owner-freebsd-stable@FreeBSD.ORG Fri Sep 17 09:21:56 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9E0D106564A for ; Fri, 17 Sep 2010 09:21:56 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 5440B8FC08 for ; Fri, 17 Sep 2010 09:21:56 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OwX8l-0004LF-1J for freebsd-stable@freebsd.org; Fri, 17 Sep 2010 11:21:55 +0200 Received: from nuclight.avtf.net ([217.29.94.29]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 17 Sep 2010 11:21:55 +0200 Received: from vadim_nuclight by nuclight.avtf.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 17 Sep 2010 11:21:55 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Vadim Goncharov Date: Fri, 17 Sep 2010 09:21:44 +0000 (UTC) Organization: Nuclear Lightning @ Tomsk, TPU AVTF Hostel Lines: 39 Message-ID: References: <201009100920.o8A9KAAp030811@fire.js.berklix.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: nuclight.avtf.net X-Comment-To: Julian H. Stacey User-Agent: slrn/0.9.9p1 (FreeBSD) Subject: Re: Policy for removing working code X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vadim_nuclight@mail.ru List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Sep 2010 09:21:56 -0000 Hi Julian H. Stacey! On Fri, 10 Sep 2010 11:20:10 +0200; Julian H. Stacey wrote about 'Re: Policy for removing working code': >>> If someone is following a RELENG_X (a.k.a -STABLE) or a RELENG_X_Y (a >>> errata fix branch), then they should be reading the stable@ list. >> >> True for RELENG_X, but not for RELENG_X_Y. They shouldn't, because all >> information for security/errata fix branch go to announce@, they don't >> need to read all noise in stable@ just for this. And, what is more important, >> they in fact don't do. So announce@ is the only choice from purely practical >> means. > One option could be a new list perhaps called eg one of > features@ > advisories@ > notifications@ > feature-notifications@ > to carry heads up notification of future feature changes / removals. > Its would be more traffic than > announce@ > but much lower traffic than > stable@ > FreeBSD already has the precedent of > security-notifications@ Umm, no: security-notifications@ is not an addon to, but rather a subset of announce@ for those who don't care about anything except the most important events - security. So announce@ would be sufficient - and Handbook already states that things like call for volunteers go to announce@ (and many feature removal notifications may be not certain if there will be volunteers then). But perhaps your idea is applicable to www.freebsd.org, though. -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight]