public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Monthly Gentoo Council Reminder for March
Date: Sat, 01 Mar 2008 13:02:03 -0500	[thread overview]
Message-ID: <47C99A1B.7020009@gentoo.org> (raw)
In-Reply-To: <47C96B1F.9000805@gentoo.org>

Raúl Porcel wrote:
> Peter Weller wrote:
>>
>> Oh, I'd be more than happy to accept help from developers like that.
>> It's just a case of what the "big bosses" think of it. Plus there's
>> the fact that some other arches operate on a "it compiles, mark it
>> stable" policy, and we don't want developers to bring that attitude to
>> the amd64 team.
> 
> Hope you're not referring to any of my arches because that's not true :)
> In fact, if i did that, i wouldn't crash the alpha dev box so often,
> right Tobias?
> 

I dunno - I just hit bug 211021 today while trying to clean out old
bugs.  Already stable on one arch and not a word from the maintainer.

I do agree with many of the posts in this thread by others - a big issue
is manpower.  However, I did want to mention that stabling packages
without input from maintainers seems to be a moderately-common practice.
 I'm sure the arch team leaders would welcome help if it were offered,
but it is more important that packages keyworded stable actually work
than for the latest-and-greatest package to be marked stable.
Interested users can volunteer to be ATs as well - in my past experience
as an AT when I keyworded a bug STABLE I could expect to see it
committed by a dev within a few hours.

While amd64 is a lot more mainstream than it used to be you can't just
assume that upstream wouldn't have released something if it didn't work
perfectly on amd64.

Somebody had commented that there are cases where there are
already-stable packages with bugs in them that are causing problems.
Feel free to ping one of us, or start a discussion on the -amd64 mailing
list, or email the amd64@ alias if necessary if something in particular
is causing major headaches.  Simply posting a comment in bug 37 out of
250 probably won't get much attention.  I'm sure all the amd64 devs want
to do what they can to help out those with more obscure packages.  There
are a LOT of packages marked stable on amd64 though, and while it has
improved greatly upstream still doesn't support it as well as it does
x86 (though I'm sure we won't get much sympathy from most of the other
archs in this regard :)  ).

No disputing that there is a problem - we just want to be careful that
the solution isn't worse than the problem...
-- 
gentoo-dev@lists.gentoo.org mailing list



  reply	other threads:[~2008-03-01 18:02 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-01  5:30 [gentoo-dev] Monthly Gentoo Council Reminder for March Mike Frysinger
2008-03-01 10:55 ` Raúl Porcel
2008-03-01 12:35   ` Richard Freeman
2008-03-01 12:56     ` [gentoo-dev] " Christian Faulhammer
2008-03-01 14:28       ` Raúl Porcel
2008-03-01 14:29   ` [gentoo-dev] " Peter Weller
2008-03-01 14:41     ` Raúl Porcel
2008-03-01 18:02       ` Richard Freeman [this message]
2008-03-01 18:45         ` [gentoo-dev] " Christian Faulhammer
2008-03-02  2:50           ` Richard Freeman
2008-03-02  3:43           ` Steve Dibb
2008-03-02  8:48             ` George Shapovalov
2008-03-02 12:34               ` Richard Freeman
2008-03-02 13:12                 ` Jan Kundrát
2008-03-03  7:32                 ` George Shapovalov
2008-03-02  9:56           ` Santiago M. Mola
2008-03-03  0:31             ` Christian Faulhammer
2008-03-01 18:47         ` [gentoo-dev] " Raúl Porcel
2008-03-01 22:33           ` Ed W
2008-03-02  2:45           ` Richard Freeman
2008-03-01 14:39   ` Peter Weller
2008-03-01 17:56     ` Peter Volkov
2008-03-05 17:11 ` Anant Narayanan
2008-03-05 17:24   ` Jean-Noël Rivasseau
2008-03-05 17:45   ` Marius Mauch
2008-03-05 18:10     ` Anant Narayanan
2008-03-06 14:08       ` Denis Dupeyron
2008-03-05 18:24     ` Thomas Anderson
2008-03-05 19:41       ` Petteri Räty
2008-03-05 20:04         ` Thomas Anderson
2008-03-05 19:59           ` Doug Goldstein
2008-03-05 20:31             ` Thomas Anderson
2008-03-05 21:05               ` Petteri Räty
2008-03-05 21:40                 ` Thomas Anderson
2008-03-05 22:09                   ` Petteri Räty
2008-03-06  3:38                 ` Anant Narayanan
2008-03-06  7:31                   ` Alec Warner
2008-03-06 12:17                   ` [gentoo-dev] proxy-maintaner improvement (was: Monthly Gentoo Council Reminder for March) Peter Volkov
2008-03-05 21:07               ` [gentoo-dev] Monthly Gentoo Council Reminder for March Doug Goldstein
2008-03-05 22:13                 ` Robin H. Johnson
2008-03-05 20:32             ` Thomas Anderson
2008-03-05 18:19   ` Donnie Berkholz
2008-03-05 20:07   ` Santiago M. Mola
2008-03-06 13:38     ` Zhang Le
2008-03-06 21:25       ` [gentoo-dev] " Markus Ullmann
2008-03-06 21:37         ` Petteri Räty
2008-03-06 23:26         ` Jorge Manuel B. S. Vicetto
2008-03-05 21:45   ` [gentoo-dev] " Josh Saddler
2008-03-06  7:38   ` Roy Marples
2008-03-06  9:02   ` Sébastien Fabbro
2008-03-06  9:15     ` Ioannis Aslanidis
2008-03-07 18:48     ` Marius Mauch
2008-03-10  5:12       ` Natanael Copa
2008-03-10  5:21         ` Alec Warner
2008-03-10  8:29           ` Roy Marples
2008-03-10 11:58             ` Denis Dupeyron
2008-03-10 10:09           ` Natanael Copa
2008-03-10 12:05         ` Peter Volkov
2008-03-10 12:13           ` Alec Warner
2008-03-10 13:39             ` Peter Volkov
2008-03-07  1:56   ` [gentoo-dev] " Ryan Hill
2008-03-06 17:31 ` [gentoo-dev] " Jeroen Roovers
2008-03-06 20:41   ` Petteri Räty
2008-03-07  4:42     ` Jeroen Roovers
2008-03-07  5:09       ` Petteri Räty
2008-03-07  7:35         ` Ulrich Mueller
2008-03-07 10:16           ` George Shapovalov
2008-03-07 12:27           ` Petteri Räty
     [not found] ` <18385.19961.449228.320972@a1i15.kph.uni-mainz.de>
     [not found]   ` <20080308154504.02af79c2@epia.jer-c2.orkz.net>
     [not found]     ` <200803081610.33774.philantrop@gentoo.org>
     [not found]       ` <20080310060849.4c2bf0c9@epia.jer-c2.orkz.net>
     [not found]         ` <47D4F26C.7050701@gentoo.org>
2008-03-10 12:00           ` [gentoo-dev] Re: [gentoo-core] Keywords policy Alec Warner
2008-03-10 13:50             ` Wulf C. Krueger
2008-03-10 14:22               ` Alec Warner
2008-03-10 15:26                 ` Wulf C. Krueger
     [not found]                   ` <20080311044938.72401cd7@epia.jer-c2.orkz.net>
2008-03-11  4:40                     ` Ryan Hill
2008-03-11 11:41                       ` Alec Warner
2008-03-11 15:24                         ` Richard Freeman
2008-03-11 19:47                           ` Ferris McCormick
2008-03-11 23:46                             ` Richard Freeman
2008-03-12  1:16                         ` Ryan Hill
     [not found]                     ` <20080311054345.26a83921@epia.jer-c2.orkz.net>
2008-03-11  5:04                       ` Ryan Hill
     [not found]                         ` <20080311063648.0ea54906@epia.jer-c2.orkz.net>
2008-03-11 11:24                           ` Peter Volkov
  -- strict thread matches above, loose matches on Subject: below --
2010-03-01  5:30 [gentoo-dev] Monthly Gentoo Council Reminder for March Mike Frysinger
2010-03-05 18:52 ` Mike Frysinger
2009-03-01  5:30 Mike Frysinger
2007-03-01  5:30 Mike Frysinger
2006-03-01  9:17 Mike Frysinger
2006-03-02  0:28 ` Mike Frysinger
2006-03-02  1:46   ` Ned Ludd

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=47C99A1B.7020009@gentoo.org \
    --to=rich0@gentoo.org \
    --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