Please find below the first draft of GLEP 83 "EAPI deprecation". This tries to define criteria for deprecation and for banning of EAPIs by the Council.
I have tried to model it in a way that the actual dates for at least EAPIs 4 and 5 are reproduced within a few months. To this end, the criteria depend on three parameters: - time between EAPI n+1 support by stable Portage and deprecation of EAPI n (24 months) - time between deprecation and ban (24 months) - fraction of ebuilds in the tree when banning (< 5 %, at present corresponding to about 1500 ebuilds) The first two parameters can be varied within a relatively wide range, without much influence on the timing for EAPIs 4 and 5. Combinations like 30/24 months, 30/18 months, 24/18 months, or even 36/12 months would work as well. I guess the question there is if we prefer a longer upgrade path and transition times, or a smaller number of EAPIs in the tree. A rendered version (which especially makes the backwards compatibility table readable) can be found here: https://github.com/ulm/glep/blob/glep-eapi-deprecation/glep-0083.rst Comments please. Ulrich --- GLEP: 83 Title: EAPI deprecation Author: Ulrich Müller <u...@gentoo.org> Type: Informational Status: Draft Version: 1 Created: 2022-06-30 Last-Modified: 2022-07-11 Post-History: 2022-07-11 Content-Type: text/x-rst --- Abstract ======== Introduce standardized criteria for deprecation and banning of EAPIs. Motivation ========== 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. Specification ============= A *deprecated EAPI* is no longer required for the upgrade path of users' systems. Its use is discouraged, and tools like pkgcheck will 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 two newer EAPIs are supported by the stable version of Portage, and one of them has been supported for 24 months. The Gentoo Council will ban a deprecated EAPI when it is used by less than 5 % of ebuilds in the Gentoo repository, but no sooner than 24 months after its deprecation. EAPIs used in profiles are outside the scope of this GLEP. Rationale ========= Timing of EAPI deprecation is a trade-off between different factors. On the one hand, the total number of EAPIs in active use should be limited; this will prevent the learning curve for new developers and contributors from becoming too steep and will help to reduce code complexity, e.g. in eclasses. On the other hand, an upgrade path to a stable system is guaranteed for one year, plus limited support for systems that are outdated more than a year [#COUNCIL-20091109]_. Therefore, previous EAPIs are still required during that time. A period of 24 months before deprecation has been chosen, which is more than the required minimum and will 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. 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. Backwards Compatibility ======================= The following table compares the actual dates of deprecations and bans [#PMS-PROJECT]_ with the dates that would have resulted from the criteria proposed in this GLEP ("new date"). .. csv-table:: :header-rows: 2 :stub-columns: 1 :widths: auto :align: right EAPI,Portage,Gentoo repo,deprecated,deprecated,diff.,banned,banned,diff. ,stable,usage < 5 %,actual date,new date,months,actual date,new date,months 0,2005-12-26,2017-02-28,2014-02-25,2009-12-11,-50,2016-01-10,2017-02-28,+14 1,2007-12-11,2009-10-25,2013-04-09,2011-01-08,-27,2014-03-11,2013-01-08,-14 2,2009-01-08,2015-03-27,2013-04-09,2012-03-08,-13,2014-03-11,2015-03-27,+12 3,2010-03-08,2015-01-16,2014-02-25,2013-03-17,-11,2016-01-10,2015-03-17,-10 4,2011-03-17,2018-01-11,2015-10-11,2016-01-17,+3,2018-04-08,2018-01-17,-3 5,2012-12-11,2021-06-15,2018-05-13,2018-06-27,+1,2021-08-08,2021-06-15,-2 6,2016-01-17,2022-11-22 [*]_,2021-07-11,2021-07-05,0,,2023-07-05, 7,2018-06-27,,,,,,, 8,2021-07-05,,,,,,, .. [*] Extrapolated date, obtained by fitting data between 2021-01-01 and 2022-07-11 with an exponential function. References ========== .. [#COUNCIL-20130409] "EAPI deprecation", Gentoo Council meeting summary 2013-04-09 (https://projects.gentoo.org/council/meeting-logs/20130409-summary.txt). Note: The original quote says "Repoman" instead of "pkgcheck". .. [#COUNCIL-20140311] "Ban on EAPI 1 and 2 should extend to updating EAPI in existing ebuilds", Gentoo Council meeting summary 2014-03-11 (https://projects.gentoo.org/council/meeting-logs/20140311-summary.txt) .. [#COUNCIL-20091109] "Upgrade path for old systems", Gentoo Council meeting summary 2009-11-09 (https://projects.gentoo.org/council/meeting-logs/20091109-summary.txt) .. [#PMS-PROJECT] Gentoo Package Manager Specification project (https://wiki.gentoo.org/wiki/Project:Package_Manager_Specification#EAPI_life_cycle) Copyright ========= This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/4.0/.
signature.asc
Description: PGP signature
