public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Bracht Laumann Jespersen <t@laumann.xyz>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP 83: EAPI deprecation
Date: Sun, 31 Jul 2022 22:08:52 +0200	[thread overview]
Message-ID: <YubhVM/2OE7/RUQg@sofaking> (raw)
In-Reply-To: <ufsihtcpa@gentoo.org>

Minor language things, on the whole an easy document to read!

> 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.

"very different" could maybe be specified further. Something like
"inconsistent"/"unreliable"/"unpredictable" is more precise?

> 
> The Gentoo Council will ban a deprecated EAPI when
> 
> * 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 %".

> 
> 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". Maybe
"although" is a better word here?

I would drop the ", in order" and make it simply "[…] an additional threshold
of 5% is required to keep the number […]"

-- Thomas


  reply	other threads:[~2022-07-31 20:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 19:25 [gentoo-dev] GLEP 83: EAPI deprecation Ulrich Mueller
2022-07-13  8:12 ` Ulrich Mueller
2022-07-13 18:50   ` Arthur Zamarin
2022-07-14  4:17     ` Sam James
2022-07-31 17:27 ` Ulrich Mueller
2022-07-31 20:08   ` Thomas Bracht Laumann Jespersen [this message]
2022-07-31 21:21     ` Ulrich Mueller
2022-07-31 21:26   ` [gentoo-dev] GLEP 83 [v3]: " Ulrich Mueller
2022-07-31 22:04     ` [gentoo-dev] " Ulrich Mueller
2022-08-01 21:24     ` Duncan
2022-08-02  4:48       ` [gentoo-dev] " Sam James
2022-08-02  5:18         ` Ulrich Mueller
2022-08-02  5:07       ` [gentoo-dev] " Ulrich Mueller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YubhVM/2OE7/RUQg@sofaking \
    --to=t@laumann.xyz \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox