public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev-announce] Council meeting summary: Tuesday 14 August 2012, 19:00 UTC
Date: Sun, 26 Aug 2012 13:37:03 +0200	[thread overview]
Message-ID: <20120826113703.GC5282@gentoo.org> (raw)
In-Reply-To: <20120807191736.GF49719@gentoo.org>

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

Apologies for sending the summary this late.


Summary of Gentoo council meeting 14th August 2012

Roll call
=========
betelgeuse
chainsaw
grobian
scarabeus
ulm
williamh

absent
------
dberkholz (receives slacker mark)


EAPI5 features
==============
Due to holidays, the list of features for EAPI5 was announced only 2
days in advance of the meeting.  This gave little time for Council
members to prepare for votes.
Therefore a vote was conducted if voting on EAPI5 features in this
meeting was deemed suitable.

The Council voted unanimously to postpone voting on EAPI5 features.

The list of features for EAPI5 were outlined by ulm in
http://thread.gmane.org/gmane.linux.gentoo.project/2101/focus=2115
Since many of these features appear not to be implemented in Portage, a
discussion on their implementation is called for by the Council.  The
Council stressed that it prefers to vote on EAPI5 features that can and
will be implemented within a short timeframe, say 1 month.


Open bugs with Council involvement
==================================
There are currently no open bugs.


Open floor
==========
scarabeus suggested the change "dev should use latest eapi when bumping"
to "dev must use latest eapi when bumping if not forbidden by eclasses".
He was asked to bring it up on the mailing lists, to get a better
definition of when what EAPI should be used.

ulm raised deprecation of EAPI 1 on request of patrick.  Arfrever argued
that backwards compatability is not an issue here, and that it can
greatly reduce code size/maintenance of eclasses when EAPI0 and EAPI1
are removed.  It was questioned whether removal of an EAPI really brings
that much benefits.  It seems eclasses can drop support for EAPIs, if
all consumers don't use them, which does not require complete removal of
the EAPI.  It appears some packages use build-systems that require
EAPI1.


Next meeting date
=================
11 September 2012, 19:00 UTC


-- 
Fabian Groffen
Gentoo on a different level

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

      reply	other threads:[~2012-08-26 15:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07 19:17 [gentoo-dev-announce] Council meeting: Tuesday 14 August 2012, 19:00 UTC Fabian Groffen
2012-08-26 11:37 ` Fabian Groffen [this message]

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=20120826113703.GC5282@gentoo.org \
    --to=grobian@gentoo.org \
    --cc=gentoo-dev-announce@lists.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