From owner-freebsd-arch@freebsd.org Sun Dec 16 19:11:10 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A6451337759 for ; Sun, 16 Dec 2018 19:11:10 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0E221930B3 for ; Sun, 16 Dec 2018 19:11:10 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: by mailman.ysv.freebsd.org (Postfix) id C33D31337758; Sun, 16 Dec 2018 19:11:09 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B1B2E1337757 for ; Sun, 16 Dec 2018 19:11:09 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FBDC930AC for ; Sun, 16 Dec 2018 19:11:09 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 7C8408D4A250; Sun, 16 Dec 2018 19:11:06 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 604FAD1F835; Sun, 16 Dec 2018 19:11:05 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id IHDCbe8VgGp9; Sun, 16 Dec 2018 19:11:03 +0000 (UTC) Received: from [192.168.1.88] (fresh-ayiya.sbone.de [IPv6:fde9:577b:c1a9:f001::2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 24D0BD1F7F3; Sun, 16 Dec 2018 19:11:02 +0000 (UTC) From: "Bjoern A. Zeeb" To: "Rodney W. Grimes" Cc: "George Neville-Neil" , freebsd- Subject: Re: A proposal for code removal prior to FreeBSD 13 Date: Sun, 16 Dec 2018 19:11:56 +0000 X-Mailer: MailMate (2.0BETAr6133) Message-ID: <261A6437-3ECC-43FF-ADA2-EE430477BB92@lists.zabbadoz.net> In-Reply-To: <201812161645.wBGGj7qn092076@pdx.rh.CN85.dnsmgr.net> References: <201812161645.wBGGj7qn092076@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4FBDC930AC X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.985,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Dec 2018 19:11:10 -0000 On 16 Dec 2018, at 16:45, Rodney W. Grimes wrote: I’ll ignore the “turning FreeBSD into change-management procedures” part. > timed was removed outside of current procedure, and that should > be corrected ASAP, No, it should not. There is a stable branch, with shipping releases, and support until at least June 30, 2020, possibly longer. The questions are: (a) will the request still be relevant then? (b) do we still want to support it then? (c) with pkgbase hopefully coming, will it still matter or is it better off to be “3rd party” software? (d) if it’s coming back, do we have a developer to care about it and take care of the original reason that triggered the removal? > as one developer has already spoken up that > they are using it. s/developer/user/ ; whether he is a developer as well is not the point. /bz