From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NYFNt-0005aE-Lr for garchives@archives.gentoo.org; Fri, 22 Jan 2010 09:00:53 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 32F39E0818; Fri, 22 Jan 2010 08:59:22 +0000 (UTC) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.31.39]) by pigeon.gentoo.org (Postfix) with ESMTP id 002F0E0818 for ; Fri, 22 Jan 2010 08:59:21 +0000 (UTC) Received: from [93.210.47.251] (helo=arkane.local) by smtprelay01.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1NYFMO-0004JL-NI for gentoo-dev@lists.gentoo.org; Fri, 22 Jan 2010 09:59:20 +0100 Received: by arkane.local (Postfix, from userid 1000) id A67185E46F; Fri, 22 Jan 2010 09:58:27 +0100 (CET) Date: Fri, 22 Jan 2010 09:58:27 +0100 From: Torsten Veller To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] EAPI-3 times and dates Message-ID: <20100122094627.TA4624b.tv@veller.net> Mail-Followup-To: gentoo-dev@lists.gentoo.org Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Face: ===_______=8)_=8)_______A_very_very_nice_face_______=8)_=8)_______=== Jabber-ID: tove@jabber.ccc.de X-PGP-Fingerprint: 0416 3C11 8D79 65B9 AAD0 2065 BBC7 14D1 9C67 CD96 User-Agent: Mutt/1.5.20 (2009-12-10) X-Df-Sender: 1067115 X-Archives-Salt: 7c7bb3ed-e505-429e-bf5e-94a430b2e7cd X-Archives-Hash: bbcaa015e03ea39326f76342b6acd894 EAPI-3 was approved by the council during their last meeting (2010-01-18). Which portage versions do support it? (I wasn't able to find it in the docs.) When can we stabilize EAPI-3 ebuilds? (I guess this is again a council decision?) How long do we have to provide ebuilds for older EAPIs? (We can drop them as long as users are able to upgrade to an EAPI-3 capable package-manager for at least one year from now/after stabilisation?) Is this worth to be documented if it isn't?