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 2014-02-25
Date: Mon, 10 Feb 2014 16:39:17 +0100	[thread overview]
Message-ID: <21240.62117.487172.995650@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <201402101545.39578.dilfridge@gentoo.org>

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

>>>>> On Mon, 10 Feb 2014, Andreas K Huettel wrote:

> In two weeks, the council will have its (well, this time only nearly
> regular) monthly meeting. Now is the time to raise and prepare items
> that the council should put on the agenda to discuss or vote on.

> Please respond to this message with agenda items. Do not hesitate to
> repeat your agenda item here with a pointer if you previously
> suggested one (since the last meeting).

Can we discuss/vote about EAPI deprecation please? Looking at the
summary of our 2013-04-09 meeting, we could take the following three
votes:

- "EAPI 3 is no longer required for the upgrade path of users' systems."
- "EAPI 3 is discouraged. Repoman should warn about this."
- "EAPI 0 is discouraged. Repoman should warn about this."

Portage 2.1.9.42 (supporting EAPI 4) went stable on the last
architecture on 2011-03-17 which was almost three years ago.

Ulrich

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

  reply	other threads:[~2014-02-10 15:39 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 14:45 [gentoo-project] Call for agenda items - Council meeting 2014-02-25 Andreas K. Huettel
2014-02-10 15:39 ` Ulrich Mueller [this message]
2014-02-10 16:00   ` Andreas K. Huettel
2014-02-10 16:22     ` Ruud Koolen
2014-02-10 18:03       ` Tom Wijsman
2014-02-10 18:49         ` Ciaran McCreesh
2014-02-10 18:51         ` Ulrich Mueller
2014-02-10 19:07 ` hasufell
2014-02-11  2:39   ` Rick "Zero_Chaos" Farina
2014-02-11 23:20     ` hasufell
2014-02-20  9:33   ` Ulrich Mueller
2014-02-20 15:46     ` hasufell
2014-02-11 19:46 ` Andreas K. Huettel
2014-02-13  4:35   ` William Hubbs
2014-02-13 11:41     ` Andreas K. Huettel
2014-02-21  3:28       ` Donnie Berkholz
2014-02-21  0:14 ` Chí-Thanh Christopher Nguyễn
2014-02-21  3:47   ` Donnie Berkholz
2014-02-21  4:03     ` Rich Freeman
2014-02-21  4:04       ` Donnie Berkholz
2014-02-21 13:32         ` Anthony G. Basile
2014-02-21  8:38     ` Michał Górny
2014-02-21 10:34       ` Tom Wijsman
2014-02-24 16:46     ` Chí-Thanh Christopher Nguyễn
2014-02-24 18:59       ` Tom Wijsman
2014-02-24 21:43         ` Chí-Thanh Christopher Nguyễn
2014-02-24 23:55           ` Tom Wijsman
2014-02-25  0:12           ` Rich Freeman
2014-02-24 23:13       ` Patrick Lauer
2014-02-24 23:54 ` Patrick Lauer

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=21240.62117.487172.995650@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