From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2014-02-25
Date: Mon, 10 Feb 2014 18:49:26 +0000 [thread overview]
Message-ID: <20140210184926.3bdf80e4@googlemail.com> (raw)
In-Reply-To: <20140210190321.0aa09e30@TOMWIJ-GENTOO>
[-- Attachment #1: Type: text/plain, Size: 693 bytes --]
On Mon, 10 Feb 2014 19:03:21 +0100
Tom Wijsman <TomWij@gentoo.org> wrote:
> Indeed, as pointed out in the other thread on -dev; there are multiple
> possibilities here:
>
> 1. an edit to an existing ebuild;
>
> 2. a revision bump;
>
> 3. a version bump.
>
> Definitely would want to ban (3), I think banning (2) might be
> possible too if we expect developers to bump EAPI as they revision
> bump (and perhaps give the exception for critical security fixes to
> not have to bump the EAPI), banning (1) gets a bit more tricky.
Bumping to EAPI 5 should always involve a revbump, to avoid a messy
situation with use dependency defaults.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-02-10 18:49 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
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 [this message]
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=20140210184926.3bdf80e4@googlemail.com \
--to=ciaran.mccreesh@googlemail.com \
--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