From: Ulrich Mueller <ulm@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - council meeting 2020-03-08
Date: Mon, 02 Mar 2020 14:51:13 +0100 [thread overview]
Message-ID: <w6gimjmdfvy.fsf@kph.uni-mainz.de> (raw)
In-Reply-To: <057597b3b2b8e8ea2deccca7e3b6f700d2aff820.camel@gentoo.org> ("Michał Górny"'s message of "Mon, 02 Mar 2020 13:46:41 +0100")
[-- Attachment #1: Type: text/plain, Size: 646 bytes --]
>>>>> On Mon, 02 Mar 2020, Michał Górny wrote:
> Not sure if this is practically able but technically I see an advantage
> from having three distinct states:
> 1. Deprecation -- tooling warns about them but there are no consequences
> for adding new ebuilds.
> 2. Ban I -- tooling errors out, if developers add new ebuilds
> (as in real new ebuilds), we pursue it.
Does this really occur at a scale that should bother us? The main
blocker for removal of old EAPIs are unmaintained ebuilds, and for
these any levels of more fine-grained bans won't help.
> 3. Ban II -- no ebuilds left, CI fatal, immediate revert.
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
next prev parent reply other threads:[~2020-03-02 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 3:59 [gentoo-project] Call for agenda items - council meeting 2020-03-08 Georgy Yakovlev
2020-03-02 11:57 ` Michał Górny
2020-03-02 12:19 ` Raymond Jennings
2020-03-02 12:38 ` Ulrich Mueller
2020-03-02 12:46 ` Michał Górny
2020-03-02 13:51 ` Ulrich Mueller [this message]
2020-03-02 14:11 ` Michał Górny
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=w6gimjmdfvy.fsf@kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=mgorny@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