public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: Donnie Berkholz <dberkholz@gentoo.org>,
	gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev-announce] Re: [gentoo-project] Agenda for Gentoo Council meeting on 2014-02-25
Date: Sat, 22 Feb 2014 02:12:53 +0100	[thread overview]
Message-ID: <201402220212.54333.dilfridge@gentoo.org> (raw)
In-Reply-To: <20140221040044.GG8819@comet.hsd1.mn.comcast.net>

Am Freitag, 21. Februar 2014, 05:00:44 schrieb Donnie Berkholz:
> I've attached a draft agenda for Tuesday's meeting. Suggestions welcome!

Re "Stable keywords on testing architectures":

The proposed solution is only touching part of the issue; it kinda ignores 
what happens to the keywords themselves. 

Anything is better than the current randomness.

Example: Ebuild maintainer wants to drop old versions, looks at eshowkw 
output, gets confused by random stable / nonstable marking.
(Enough people have asked me in the last weeks.)

* drop em all
* just revert our previous decision as we wont push it anyway
* come up with some compromise and define what package maintainers can / 
cannot do

-- 
Andreas K. Huettel
Gentoo Linux developer (council, kde)
dilfridge@gentoo.org
http://www.akhuettel.de/


      reply	other threads:[~2014-02-22  1:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21  4:00 [gentoo-dev-announce] Agenda for Gentoo Council meeting on 2014-02-25 Donnie Berkholz
2014-02-22  1:12 ` Andreas K. Huettel [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=201402220212.54333.dilfridge@gentoo.org \
    --to=dilfridge@gentoo.org \
    --cc=dberkholz@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