From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JVW2G-000754-3J for garchives@archives.gentoo.org; Sat, 01 Mar 2008 18:02:12 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5B27FE068C; Sat, 1 Mar 2008 18:02:10 +0000 (UTC) Received: from vms040pub.verizon.net (vms040pub.verizon.net [206.46.252.40]) by pigeon.gentoo.org (Postfix) with ESMTP id 44186E068C for ; Sat, 1 Mar 2008 18:02:10 +0000 (UTC) Received: from gw.thefreemanclan.net ([71.242.211.138]) by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JX200MOECVZ1GZD@vms040.mailsrvcs.net> for gentoo-dev@lists.gentoo.org; Sat, 01 Mar 2008 12:04:49 -0600 (CST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by gw.thefreemanclan.net (Postfix) with ESMTP id 5E8DF1240CA for ; Sat, 01 Mar 2008 13:02:03 -0500 (EST) Date: Sat, 01 Mar 2008 13:02:03 -0500 From: Richard Freeman Subject: Re: [gentoo-dev] Monthly Gentoo Council Reminder for March In-reply-to: <47C96B1F.9000805@gentoo.org> To: gentoo-dev@lists.gentoo.org Message-id: <47C99A1B.7020009@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 References: <20080301103002.A2AE266A22@smtp.gentoo.org> <47C9360A.9080806@gentoo.org> <200803011429.39223.welp@gentoo.org> <47C96B1F.9000805@gentoo.org> User-Agent: Thunderbird 2.0.0.12 (X11/20080301) Content-Transfer-Encoding: quoted-printable X-Archives-Salt: be068066-16dc-4ea5-b572-0c98212ae981 X-Archives-Hash: baf0bb0bb76fde851eed1c4fdb41fcd5 Ra=FAl 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. >=20 > 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? >=20 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... --=20 gentoo-dev@lists.gentoo.org mailing list