public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gmail.com>
To: justin <jlec@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] making the stable tree more up-to-date
Date: Fri, 16 Dec 2011 03:07:46 -0800	[thread overview]
Message-ID: <20111216110746.GA5571@localhost.hobnob.com> (raw)
In-Reply-To: <4EEB2087.2050608@gentoo.org>

On Fri, Dec 16, 2011 at 11:42:15AM +0100, justin wrote:
> Hi,
> 
> I really like that you open all those bugs. But it makes no sense to add
> arches after a "time out". At least not after a such a short one. The
> maintainer is responsible for the package, that means it is their
> responsibility to decide that a package should go stable.

Might want to include data on "short time out".  If said timeout also 
occured despite a dev being away, that also would be relevant.

Personally, having been on the receiving end of it I don't mind it- 
the timeout approach is good for getting procrastrinating 
and/or overloaded maintaners to speak up rather than the bug rotting.


> In addition
> they have to make the package fit to the standards that the arch teams
> request. And I can tell from my own experience it is always more than
> the average package has.

Eh?  Tree standards apply, if the ebuild isn't yet to that point, than 
it should be sorted prior to unstable /anyways/.  If an arch has 
special standards, and they want the pkg stabled, it's on the *arch* 
to do the legwork if the requirements are daft, else tell the arch to 
be less retarded.  My view at least.

I *suspect* the requirements you're complaining about here are more 
related to source quality/running on alternate arches rather than 
packaging itself- either way clarification is useful.


> So as long as you don't review the packages
> yourself, consider a different proceeding than this timeout.
> 
> Please remove all added arches from the packages maintained by all sci*
> teams.

I have no issues w/ people bypassing me if I'm not doing my job in a 
timely fashion- with the caveat that anyone doing so has to keep what 
they kill (you break it, you fix it; if I'm overloaded someone 
making a mess and dumping it in my lap will result in a fair bit of 
hell directed their way).

~harring



  parent reply	other threads:[~2011-12-16 11:08 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  8:41 [gentoo-dev] making the stable tree more up-to-date "Paweł Hajdan, Jr."
2011-11-21 11:48 ` Ulrich Mueller
2011-11-21 12:14 ` Andreas K. Huettel
2011-11-21 12:24   ` "Paweł Hajdan, Jr."
2011-11-21 12:27   ` Rich Freeman
2011-11-21 13:12 ` James Broadhead
2011-11-21 15:47 ` Brian Dolbec
2011-11-23 14:27 ` [gentoo-dev] " Torsten Veller
2011-11-24 15:17   ` "Paweł Hajdan, Jr."
2011-11-24 16:35     ` Ian Stakenvicius
2011-11-24 17:12       ` Rich Freeman
2011-11-24 17:26         ` Pacho Ramos
2011-11-29 12:18         ` "Paweł Hajdan, Jr."
2011-11-25 16:39 ` [gentoo-dev] " Thomas Kahle
2011-11-25 19:06   ` Mr. Aaron W. Swenson
2011-11-29 12:17   ` "Paweł Hajdan, Jr."
2011-12-16 10:42 ` justin
2011-12-16 11:06   ` Agostino Sarubbo
2011-12-16 11:10     ` Anthony G. Basile
2011-12-16 11:21       ` Agostino Sarubbo
2011-12-16 11:46         ` justin
2011-12-18 10:59           ` [gentoo-dev] checking C*FLAGS used for build (was: making the stable tree more up-to-date) Michał Górny
2011-12-16 11:07   ` Brian Harring [this message]
2011-12-16 13:27   ` [gentoo-dev] making the stable tree more up-to-date "Paweł Hajdan, Jr."
2011-12-16 13:53     ` Rich Freeman
2011-12-16 14:05       ` Andreas K. Huettel
2011-12-16 18:40         ` Tim Harder
2011-12-16 14:12     ` justin
2011-12-17 15:25       ` "Paweł Hajdan, Jr."

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=20111216110746.GA5571@localhost.hobnob.com \
    --to=ferringb@gmail.com \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=jlec@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