Re: [gentoo-project] Call for agenda items - Council meeting 2018-04-08

[Ulrich Mueller <ulm@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]

>>>>> On Thu, 29 Mar 2018, Michał Górny wrote:

> Next item: provided that EAPI 7 is approved, we'd have 4 'live' EAPIs
> in motion [1]. I'd like therefore request the Council to vote on:

> a. banning EAPI 4 for new ebuilds (and EAPI bumps of existing ebuilds).
> It has been deprecated on 2015-10-11. In the past, deprecated EAPIs were
> banned within 11/23 months from deprecation, so we're overdue.

Fine with me.

> 2. deprecating EAPI 5. In case of EAPIs 3-4 they were deprecated 4-5
> years after being added.

I think a better indicator is the time between support for EAPI n+1 in
stable Portage, and deprecation of EAPI n (see [1]). Using this, I get
37 months for EAPI 2, 35 months for EAPI 3, and 34 months for EAPI 4
deprecation.

> EAPI 6 has been added on 2015-11-13, and even toolchain team already
> uses it, so there's really no reason to use EAPI 5 anymore.

Stable Portage supports EAPI 6 since 2016-01-17, i.e. since 26 months.
So we would be somewhat on the early side.

What worries me more is that deprecation of EAPI 5 would apply to
profiles too. However, all profiles are still at EAPI 5 at this point,
and I don't see any value in upgrading them to EAPI 6.

Ulrich

> [1]:https://wiki.gentoo.org/wiki/Project:Package_Manager_Specification#Council_approval_and_use_in_Gentoo_repository

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]