glep-0083: Allow deprecation when only one newer EAPI exists

Approved by the council on 2024-09-08.

Closes: https://bugs.gentoo.org/938755
Signed-off-by: Ulrich Müller <ulm@gentoo.org>

1 files changed, 25 insertions, 8 deletions

diff --git a/glep-0083.rst b/glep-0083.rst
index 38b4e57..3b538ee 100644
--- a/glep-0083.rst
+++ b/glep-0083.rst
@@ -4,10 +4,10 @@ Title: EAPI deprecation
 Author: Ulrich Müller <ulm@gentoo.org>
 Type: Informational
 Status: Active
-Version: 1
+Version: 2
 Created: 2022-06-30
-Last-Modified: 2022-08-14
-Post-History: 2022-07-11, 2022-07-31
+Last-Modified: 2024-09-08
+Post-History: 2022-07-11, 2022-07-31, 2024-08-30, 2024-09-01
 Content-Type: text/x-rst
 ---
 
@@ -38,11 +38,12 @@ warn about this [#COUNCIL-20130409]_.
 A *banned EAPI* must no longer be used, neither for new ebuilds, nor
 for updating of existing ebuilds [#COUNCIL-20140311]_.
 
-The Gentoo Council will deprecate an EAPI when
+The Gentoo Council will deprecate an EAPI when one or more newer
+Council-approved EAPIs are supported by the stable version of Portage,
+namely
 
-* two newer Council-approved EAPIs are supported by the stable version
-  of Portage, and
-* one of them has been supported for 24 months.
+* two newer EAPIs, one of them supported for at least 24 months, or
+* one newer EAPI, supported for at least 48 months.
 
 The Gentoo Council will ban a deprecated EAPI when
 
@@ -70,7 +71,9 @@ allow projects to support a longer upgrade path.
 
 Requiring two newer EAPIs before deprecation will allow ebuilds that
 are otherwise seldom updated to be bumped to the next but one EAPI
-immediately.
+immediately.  However, deprecation of an EAPI should not be deferred
+forever, so it can be effected after a longer waiting period of 48
+months even if only one newer EAPI exists at that point.
 
 A delay of 24 months between deprecation and ban will give ebuild
 authors enough time to update.  This is especially relevant for
@@ -81,6 +84,20 @@ ebuild updates (and bug reports requesting them) manageable, as a
 banned EAPI is sufficient reason for updating an ebuild.
 
 
+Example
+=======
+
+Under this policy, EAPI 7 will be deprecated when either
+
+* Portage has supported EAPI 8 for 24 months, and supports another
+  later EAPI (e.g. EAPI 9), or
+* Portage has supported EAPI 8 for 48 months.
+
+Portage has supported EAPI 8 since 2021-07-05.  The first condition
+would be fulfilled after 2023-07-05, as soon as an EAPI 9 is also
+supported.  The second condition would be fulfilled after 2025-07-05.
+
+
 Backwards Compatibility
 =======================