From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [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 5755C158094 for ; Sun, 31 Jul 2022 21:21:51 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D95B02BC050; Sun, 31 Jul 2022 21:21:46 +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) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D6818E0FAB for ; Sun, 31 Jul 2022 21:21:45 +0000 (UTC) From: Ulrich Mueller To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] GLEP 83: EAPI deprecation In-Reply-To: (Thomas Bracht Laumann Jespersen's message of "Sun, 31 Jul 2022 22:08:52 +0200") References: Date: Sun, 31 Jul 2022 23:21:39 +0200 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) 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-sha256; protocol="application/pgp-signature" X-Archives-Salt: dd7dfdcc-1ccd-4ba0-8ded-57eaf1c62400 X-Archives-Hash: 215b43136a04e5716f43ec20b1b377e6 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable >>>>> On Sun, 31 Jul 2022, Thomas Bracht Laumann Jespersen wrote: > Minor language things, on the whole an easy document to read! >> Motivation >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>=20 >> So far, old EAPIs were deprecated by the Gentoo Council in an ad-hoc >> manner. No fixed criteria were used, resulting in very different >> deprecation times after approval of newer EAPIs. Standardized >> criteria for deprecation and banning will make the life cycle of EAPIs >> more predictable. > "very different" could maybe be specified further. Something like > "inconsistent"/"unreliable"/"unpredictable" is more precise? >>=20 >> The Gentoo Council will ban a deprecated EAPI when >>=20 >> * 24 months have passed since its deprecation, and >> * it is used by less than 5 % of ebuilds in the Gentoo repository. > Should be "fewer than 5 %". >>=20 >> A delay of 24 months between deprecation and ban will give ebuild >> authors enough time to update. This is especially relevant for >> overlays and downstream distributions. Since a banned EAPI is >> sufficient reason for updating an ebuild, an additional threshold of >> 5 % is required, in order to keep the number of such updates (and bug >> reports requesting them) manageable. > Two things: > "Since" has a temporal meaning, but is often used to mean "although". May= be > "although" is a better word here? > I would drop the ", in order" and make it simply "[=E2=80=A6] an addition= al threshold > of 5% is required to keep the number [=E2=80=A6]" Thanks, should be all fixed. Updated version will follow. Ulrich --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQFDBAEBCAAtFiEEtDnZ1O9xIP68rzDbUYgzUIhBXi4FAmLm8mMPHHVsbUBnZW50 b28ub3JnAAoJEFGIM1CIQV4u4dAH/0/vlR+TRX6hvXq1QY5Tieqp9pQEc7RgVBCT gargA/AxYDE9UBOUShKyyM99xbIFuEjTnweH4/7YOhHq+4olehnwEjaiFVgQkQNX kaRTQ0BABOh13XgBScdUlcv+ARx3E4dAroH+LIwWD/atxEKYfpO5Axsjemdz2YPP vIITD/umMkf66L10Iz8F3LfEiQa3+AkoOuUlBmTR5mC4i3NdjM3hjtUc7jiEU29H lzQqlCsGQU+HPQRT3xn1Mtt8NomMCBqz1pRiOuQgMdqQCQmXr5DLmJciMs0QtXw3 Go3EzxGPkFhtlsgpcqXcIOMjaM3ekfkG3KLyYEUu2QdGV19JAuo= =3vdB -----END PGP SIGNATURE----- --=-=-=--