public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Council meeting 19 April 2010
Date: Thu, 8 Apr 2010 05:02:25 -0700	[thread overview]
Message-ID: <20100408120225.GG10006@hrair> (raw)
In-Reply-To: <19388.19166.779165.480708@a1i15.kph.uni-mainz.de>

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

On Wed, Apr 07, 2010 at 11:05:34AM +0200, Ulrich Mueller wrote:
> Next monthly council meeting will be at 19 April 2010, 18:00 UTC
> in #gentoo-council.
> 
> If you have any topics you want us to discuss or even vote about,
> simply followup to this message.

VALID_USE-
http://archives.gentoo.org/gentoo-dev/msg_b0e868626019f497eba47194c34e5421.xml

Historically, no PMS change has been glep'ified, but if the council 
wants PMS changes to start being glep'd I'd be willing to guinea pig 
this one- earliest I'd have the glep out the door is saturday also.

Few additional notes to the proposal-
1) few has offered up his time patch wise.
2) if he backs out, I'll throw in a gurantee of having it done prior 
to the next council meeting (realistically I can do it faster, I just 
have other fish I'd like to be frying).
3) dev feedback generally has been positive, exempting ciaran's views 
on it- please review those (if you'd like a summation I can provide 
one).
4) if there are questions re: use cycle breaking or other bits, feel 
free to ask prior please- council meeting times unfortunately right 
now intersect badly with my paying work so it's hard to be online to 
answer questions during the meeting (that said per the norm I'll try).
5) final reminder- part of the impetus of this is that if this is 
punted till EAPI5, it forces pkg_pretend as the interim use constraint 
checking- this has some nasty implications on the use cycle breaking 
intentions since it would require everyone to upgrade their ebuilds to 
EAPI5 if they've got use state constraints.  Basically screws things 
up a bit and requires a potentially pointless EAPI bump for the sake 
of trying to knock EAPI4 out the door now (regardless of how long it 
takes to stable portage for it) rather than adding a few weeks in.

Thanks-
~harring

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

  parent reply	other threads:[~2010-04-08 12:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07  9:05 [gentoo-dev] Council meeting 19 April 2010 Ulrich Mueller
2010-04-07 14:23 ` Ben de Groot
2010-04-07 15:00   ` Denis Dupeyron
2010-04-07 17:14     ` Ben de Groot
2010-04-07 18:05       ` Denis Dupeyron
2010-04-07 18:22         ` Ben de Groot
2010-04-09 14:51         ` Dror Levin
2010-04-10 13:47           ` Petteri Räty
2010-04-07 21:02       ` Arun Raghavan
2010-04-07 21:45         ` Ben de Groot
2010-04-07 22:30     ` Richard Freeman
2010-04-08  1:27       ` Denis Dupeyron
2010-04-10 15:36     ` Petteri Räty
2010-04-08 11:41 ` Petteri Räty
2010-04-08 12:02 ` Brian Harring [this message]
2010-04-08 13:29   ` Ciaran McCreesh
2010-04-08 14:08     ` Patrick Lauer
2010-04-08 14:14       ` Ciaran McCreesh
2010-04-11  2:51   ` Brian Harring

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=20100408120225.GG10006@hrair \
    --to=ferringb@gmail.com \
    --cc=gentoo-dev@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