public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items -- Council meeting 09-10-2012
Date: Fri, 5 Oct 2012 10:46:36 +0200	[thread overview]
Message-ID: <20590.40556.939437.204618@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <506E8197.8060504@gentoo.org>

>>>>> On Fri, 05 Oct 2012, Patrick Lauer wrote:

> I would suggest adding a repoman warning for adding new ebuilds with
> EAPI={1,2,3} now, turn that into an error for EAPI 1 in a short time
> (3 months?), then do the same for EAPI 2 a short while later with a
> longer timeline (as there are substantially more ebuilds with EAPI 2)

I don't see any advantage in deprecating intermediate EAPIs, before we
deprecate EAPI 0. What problem are you trying to solve?

Ulrich


  reply	other threads:[~2012-10-05  9:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25  9:24 [gentoo-project] Call for agenda items -- Council meeting 09-10-2012 Fabian Groffen
2012-09-25  9:59 ` Ulrich Mueller
2012-09-27  6:19   ` Ulrich Mueller
2012-09-27 22:13     ` Brian Harring
2012-09-28  0:14       ` Ulrich Mueller
2012-09-28 12:12         ` Brian Harring
2012-10-03  5:04       ` Donnie Berkholz
2012-10-03  6:44         ` Ulrich Mueller
2012-10-03  6:56           ` Matt Turner
2012-10-03  8:31             ` Ulrich Mueller
2012-09-29 15:51     ` Ciaran McCreesh
2012-09-29 16:04       ` Ulrich Mueller
2012-09-29 16:10         ` Ciaran McCreesh
2012-09-25 19:32 ` Pacho Ramos
2012-10-02 11:30   ` Fabian Groffen
2012-10-03 17:18     ` Pacho Ramos
2012-10-04 18:32       ` Pacho Ramos
2012-10-05  6:28         ` Fabian Groffen
2012-10-05  6:41           ` Pacho Ramos
2012-10-05  6:43           ` Patrick Lauer
2012-10-05  8:46             ` Ulrich Mueller [this message]
2012-10-05 10:31               ` Rich Freeman
2012-10-05 14:51                 ` Jeff Horelick
2012-10-05 17:35                 ` Pacho Ramos

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=20590.40556.939437.204618@a1i15.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=gentoo-project@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