From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (unknown [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id C433C15802E for ; Wed, 26 Jun 2024 00:17:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id F2B9C2BC07A; Wed, 26 Jun 2024 00:17:29 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B01D82BC077 for ; Wed, 26 Jun 2024 00:17:29 +0000 (UTC) From: Sam James To: Arthur Zamarin Cc: gentoo-dev@lists.gentoo.org Subject: On the value (or not?) of stable keywords (Re: [gentoo-dev] Arch Status and Future Plans) In-Reply-To: <75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org> (Arthur Zamarin's message of "Tue, 25 Jun 2024 20:33:05 +0300") Organization: Gentoo References: <75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org> Date: Wed, 26 Jun 2024 01:17:24 +0100 Message-ID: <875xtwpnfv.fsf@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Archives-Salt: 42dfa4b7-f1dd-4d64-b1f0-f23bb020c99b X-Archives-Hash: 9ffced99712b42187e07ba62a91ccc6b --=-=-= Content-Type: text/plain Arthur Zamarin writes: > Hi all, this will be a long mail, and might be confusing, I'll try to > organize it, but this is a mess, so bear with me. > > [...] > ======== 32-bit arches ======== > > This includes stable arches x86, arm, ppc, sparc32, dev arches s390, and > maybe more. Those are in much worse situation, with a mess on various > fronts, some of them super hard to continue support. For example > qtwebengine is less and less likely to manage to compile on a > real-hardware, and not 32-bit chroot on 64-bit host. Arch Team want to > minimize our work on those arches, meaning mass-destable and even > mass-dekeyword, with potentially full drop of stable status. On stable keywords, there's a few thoughts I have: * Stable keywords help keep a platform sustainable because you can keep it up to date and not be buried under heavy updates (e.g. I sometimes get asked to not keyword new GCC versions for the benefit of ~arch-only arches) * For arches without stable keywords, we don't have any reason to regularly run the testsuite, so issues which might even be trivially solvable go unnoticed. It goes from "running tests whenever there's a regular stablereq" -> "once in a blue moon if rekeywording is required". This part is a shame, but it's also precisely why there's pressure to destable things. It's tricky :( --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iOUEARYKAI0WIQQlpruI3Zt2TGtVQcJzhAn1IN+RkAUCZnteFV8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MjVB NkJCODhERDlCNzY0QzZCNTU0MUMyNzM4NDA5RjUyMERGOTE5MA8cc2FtQGdlbnRv by5vcmcACgkQc4QJ9SDfkZBkOwEAwlKRu/62+i/vOYVHSlUHG0A86UGQF+lO4Rrw AFZuM5oA/01NusUsx/36RjkJnTeynZqHFlYrWrQRmF9LQz3KMzAL =Qb1B -----END PGP SIGNATURE----- --=-=-=--