public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich@thefreemanclan.net>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Maximum number of EAPIs in tree (was: Call For Agenda Items - 10 Jun 2014)
Date: Thu, 29 May 2014 19:27:12 -0400	[thread overview]
Message-ID: <CAGfcS_mvOScs5Jm+fh5h6MLKBrGmFR5bRBySA=JvTJC5U3gF-g@mail.gmail.com> (raw)
In-Reply-To: <21383.43664.36377.507080@a1i15.kph.uni-mainz.de>

On Thu, May 29, 2014 at 5:45 PM, Ulrich Mueller <ulm@gentoo.org> wrote:
>>>>>> On Thu, 29 May 2014, Andreas K Huettel wrote:
>
>> Let's decide that the maximum number of EAPIs allowed in the portage
>> tree at any time must not exceed 7.
>
>> 7, since then EAPI=6 can still go ahead as planned.
>
>> Any new plans afterwards can only proceed if EAPI=1 is finally gone
>> (achievable), and for more improvements the bar gets a bit higher
>> afterwards.
>
> That's tree policy, but doesn't prevent PMS and package managers from
> supporting more than that number of EAPIs.
>
> In fact, we could finalise the new EAPI, but devs would only be
> allowed to commit such ebuilds to the tree when one of the old EAPIs
> is gone. Nice way to increase peer pressure. :-)

I like the idea of controlling the number of EAPIs in the tree.  I
don't like doing it this way.

If the Council thinks there are too many EAPIs, then don't approve any
more until it is fixed.  Having everybody starting flamewars on the
list about fixing their ebuilds or don't touch my ebuilds or whatever
because projects are stepping on each other's toes seems like
dereliction of duty on the part of the Council.  What's the point of
having an elected body to make decisions if they're just going to say,
"here you go, we created a mess for you, now figure out how to sort it
out and let us know if you have any agenda items for next month...?"

I'm all for picking a guideline like 7, but in the end the same
council that sets the limit can change the limit or ignore the limit.
It is like having Congress set a budget limit - they can change the
limit as quickly as they set it, and they can even do it in the same
law that goes over the limit.

The Council has already taken measures to start deprecating EAPIs, and
I'd hope the next Council will continue this in a sensible fashion.
However, we can't dictate what they'll do, and if there is a good
reason for the number to be 8 then they can make it 8.

Rich


  reply	other threads:[~2014-05-29 23:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGfcS_nydQyxTBw1h0J37o2k7hTRDCdEyy=z=f02geLtauy++Q@mail.gmail.com>
2014-05-29 13:56 ` [gentoo-project] Re: [gentoo-dev-announce] Call For Agenda Items - 10 Jun 2014 Ulrich Mueller
2014-05-29 19:03 ` Andreas K. Huettel
2014-05-29 21:45   ` [gentoo-project] Maximum number of EAPIs in tree (was: Call For Agenda Items - 10 Jun 2014) Ulrich Mueller
2014-05-29 23:27     ` Rich Freeman [this message]
2014-05-30  0:11       ` Jeroen Roovers
2014-05-30  1:31         ` Rich Freeman
2014-05-30  1:33       ` Ulrich Mueller
2014-06-05 16:06   ` [gentoo-project] Re: [gentoo-dev-announce] Call For Agenda Items - 10 Jun 2014 Richard Yao
2014-06-05 16:42     ` Brian Dolbec
2014-06-05 16:55       ` Rich Freeman
2014-06-05 16:56     ` Tom Wijsman
2014-06-03 22:02 ` Andreas K. Huettel
2014-06-07 17:35   ` Roy Bamford
2014-06-07 20:05     ` Rich Freeman
     [not found] ` <CAGfcS_nkawNaJ58cFh1bezQOWe_kNczDfkBC=J0+zEu2chMg4Q@mail.gmail.com>
2014-06-05  6:10   ` [gentoo-project] [gentoo-dev-announce] " 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='CAGfcS_mvOScs5Jm+fh5h6MLKBrGmFR5bRBySA=JvTJC5U3gF-g@mail.gmail.com' \
    --to=rich@thefreemanclan.net \
    --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