X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mx1.tetrasec.net (mx1.tetrasec.net [74.117.190.25]) by lists.alpinelinux.org (Postfix) with ESMTP id 774AEF85513 for ; Thu, 4 Apr 2019 09:25:32 +0000 (UTC) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 938DD9E1D73 for ; Thu, 4 Apr 2019 09:25:31 +0000 (UTC) Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id 051099E0078 for ; Thu, 4 Apr 2019 09:25:30 +0000 (UTC) Date: Thu, 4 Apr 2019 11:25:25 +0200 From: Natanael Copa To: Alpine Development Subject: [alpine-devel] Should we drop armhf (armv6) support with 3.10 release? Message-ID: <20190404112525.4b04fdeb@ncopa-desktop.copa.dup.pw> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-alpine-linux-musl) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi, I wonder if can drop armhf (armv6) support with the 3.10 release, now that we have armv7? In practice it means that we no longer support Raspberry PI 1 and Zero. We will still support those with alpine v3.9 for another year. I believe dropping armhf (armv6) will save some resources when it comes to managing build servers, disk space, spending time on fixing armhf specific problems. We may also optimize the vanilla kernel better for armv7, which currently uses same config as armv6. What do you think, can we drop armhf for v3.10 or should we wait til v3.11? -nc --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---