From owner-freebsd-ports@freebsd.org Sun Aug 11 23:50:04 2019 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EA980C8D78 for ; Sun, 11 Aug 2019 23:50:04 +0000 (UTC) (envelope-from martin@waschbuesch.de) Received: from relay01.waschbuesch.it (relay01.waschbuesch.it [IPv6:2a00:cba0:100::231]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "*.waschbuesch.it", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 466G1S2bVQz4Zxq for ; Sun, 11 Aug 2019 23:50:03 +0000 (UTC) (envelope-from martin@waschbuesch.de) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=waschbuesch.de; s=dkim; h=Message-Id:In-Reply-To:To:References:Date:Subject :Mime-Version:Content-Transfer-Encoding:Content-Type:From:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=5x/GLqQ/ykGM1/aCyQiL3V/cwBBkYvOk3vPra6jim24=; b=NPzrQVfmi6yqHLzwgDzH1dgqqi 66MVZ6K+98QNf57RA/CURF1u6mj+Fs/ZPqeEZQgy56KRrnjGrzdXQ8JGINMm1/7JpMkFd1WfJzn8L LSvg9dBu+ga7lZOBI2dGgAcRaHw9QZO8vCfw8zNbAeT/OHLqxwpVZBr5rtmyvpDMBJpw=; Received: by relay01.waschbuesch.it with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim) (envelope-from ) id 1hwxb8-000KDK-3k for freebsd-ports@freebsd.org; Sun, 11 Aug 2019 23:50:02 +0000 From: =?utf-8?Q?Martin_Waschb=C3=BCsch?= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: PHP version retirement Date: Mon, 12 Aug 2019 01:50:02 +0200 References: <64faf143-bae3-378c-3ee2-b196c2ea4111@astart.com> <16731AF5-68E9-4E41-8D21-CF5917BE32A4@waschbuesch.de> <20190810231216.GA23293@lyxys.ka.sub.org> To: FreeBSD Ports In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3445.104.11) X-Rspamd-Queue-Id: 466G1S2bVQz4Zxq X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=waschbuesch.de header.s=dkim header.b=NPzrQVfm; dmarc=pass (policy=none) header.from=waschbuesch.de; spf=pass (mx1.freebsd.org: domain of martin@waschbuesch.de designates 2a00:cba0:100::231 as permitted sender) smtp.mailfrom=martin@waschbuesch.de X-Spamd-Result: default: False [-4.08 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[waschbuesch.de:s=dkim]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; MV_CASE(0.50)[]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[waschbuesch.de:+]; RCVD_IN_DNSWL_MED(-0.20)[1.3.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.0.a.b.c.0.0.a.2.list.dnswl.org : 127.0.5.2]; DMARC_POLICY_ALLOW(-0.50)[waschbuesch.de,none]; NEURAL_HAM_SHORT(-0.88)[-0.878,0]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-0.00)[country: DE(-0.01)]; ASN(0.00)[asn:21476, ipnet:2a00:cba0::/32, country:DE]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Aug 2019 23:50:05 -0000 Hi Adam, > Am 11.08.2019 um 23:22 schrieb Adam Weinberger : >=20 > On Sun, Aug 11, 2019 at 1:05 PM Franco Fichtner = wrote: >>=20 >> Quarterly is essentially useless if the decision is to immediately = axe a deprecated release. 3 months are nothing in production = environments, if you get 3 months (1,5 months mean) at all and also all = other updates and security relevant bug fixes in the same quarterly that = you desperately need. >>=20 >> Yeah, we know that won=E2=80=99t happen so please don=E2=80=99t = suggest it. >>=20 >> That deprecation policy is nice and well all by itself except when it = wreaks havoc over the ports infrastructure like in the case of PHP = version support where numerous ports are immediately unavailable and = incompatible with upgrades. >>=20 >> Furthermore, the argument that it is more more work to maintain an = abandoned version is silly because it=E2=80=99s more work to delete a = port that to just keep it in the tree for a while longer. >=20 > That last part isn't correct. The work of deleting the ports is > largely automated and simple, and it will always happen eventually. > The work involved is in supporting unsupported versions. Our php team > is spread very thin, and they simply cannot support php versions > outside of upstream development. There are no resources to backport > fixes that may or may not be designed to work with older versions I do not understand this. At all. And I sort of hope I misunderstood you, because it sounds like you think = a maintainer is or may be regarded as someone who can be expected to = provide product support of some kind? I find that notion worrying to say the least. I cannot speak for others, but my expectation is exactly that which is = found in the BSD license: That software is provided AS IS. Also, neither I, nor Franco, I suspect, are talking about backports the = way e.g. Debian is doing it. (Indeed, the word backports was introduced = in this discussion by someone else.) The point being made is that the end of upstream development on a piece = of software should not, in and of itself, be sufficient grounds for its = removal from ports. It does not cease to be useful a couple of weeks after its latest = release simply because there is no one actively developing it anymore. Martin=