From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.3/8.13.3) with ESMTP id j29GbgBg017839 for ; Wed, 9 Mar 2005 16:37:42 GMT Received: from lennier.cc.vt.edu ([198.82.162.213]) by smtp.gentoo.org with esmtp (Exim 4.42) id 1D94Bo-00052Y-Kn for gentoo-dev@robin.gentoo.org; Wed, 09 Mar 2005 16:37:40 +0000 Received: from zidane.cc.vt.edu (IDENT:mirapoint@evil-zidane.cc.vt.edu [10.1.1.13]) by lennier.cc.vt.edu (8.12.11/8.12.11) with ESMTP id j29GbfU5025384 for ; Wed, 9 Mar 2005 11:37:41 -0500 Received: from [192.168.1.2] (68-232-97-125.chvlva.adelphia.net [68.232.97.125]) by zidane.cc.vt.edu (MOS 3.5.7-GR) with ESMTP id CSV05837 (AUTH spbecker); Wed, 9 Mar 2005 11:37:40 -0500 (EST) Message-ID: <422F2659.4080005@gentoo.org> Date: Wed, 09 Mar 2005 11:37:45 -0500 From: "Stephen P. Becker" User-Agent: Mozilla Thunderbird 1.0 (X11/20041208) X-Accept-Language: en-us, en Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-To: gentoo-dev@gentoo.org MIME-Version: 1.0 To: gentoo-dev@robin.gentoo.org Subject: Re: [gentoo-dev] Please follow keywording policy References: <20050308185536.58ecbe3c@enterprise.weeve.org> <422EA7E2.4040206@gentoo.org> <422EFCA6.2010607@gentoo.org> <422F0D2E.1040301@gentoo.org> In-Reply-To: <422F0D2E.1040301@gentoo.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 494ecd19-f01c-486a-9209-609eb72a47c0 X-Archives-Hash: bd603a97dc971cf2d3304ca3acf3a3f8 > Ok, I could understand that none of the mips team are online when I > want, but how about the bug mentioned above? One month I > waited/begged/threat!!! For what? For some lousy script updates, which > is not arch dependent anyway! There are lots of open bugs, sometimes they slip under the radar. And *never* assume scripts are arch independant. See more below... > Not every package that I maintain is tested by me! How can I test a dsl > driver when I have no such device! Do you have somebody in your herd test it that does have such a device? If not, you shouldn't be maintaining it. > I apply the good old rule that if a package has no open bugs for a > month, it will be marked as stable. This if fine if you can vouch that it works. None of us could say rp-pppoe works. What is more, just because it works on x86 doesn't mean there aren't problems with other arches. Even things like perl/python/ scripts are included in this statement. If I remember correctly, ciaran even ran into a non-portable vim script at one point. That said, since you are the package maintainer, you should be practically the world's expert on this package. You should know if there are potential endian problems. You should be talking to upstream to find these sorts of things out. If you have full confidence that it should be stable on our arch, mark it stable. Seeing as you see fit to break policy and mark your dsl driver package stable even though you can't test it, then how is this any different? Keep in mind that I'm pretty sure there are developer machines available for (almost) every arch now. Package maintainers should use this resource for testing purposes. > If I would do things you way, in this moment net-dialup would have at > least 100 opened bugs with no one carrying about them. I urge you to > look in bugzilla to see how many rightfully complaints are there > regarding my work. Not as if I consider less about a dev who made a > mistake (only who do nothing, does no mistakes)... You are missing the point. > It is OK to want to make more than a simple compile test, but from this > to doing nothing when a fellow dev ask you to IS a big distance! A > convenient excuse, nothing more... Convenient excuse for what? Do you think we singled you out and said, "hey, I don't like that mrness...we're just going to ignore his package" ? > I didn't wanted to get so involved in this bug, but invalid bug reports > started by the transition from -r2 are killing me. In rest, what do I > care that your arch is outdated! I don't quite see what the big deal is anyway. When I looked, the last stable version of that package was from last november or so. If we were a year out of date or something, that might be a different story. We do have a script that emails all of the mips team with outdated packages from time to time, however we have a shortage of devs and time, so non-crucial stuff that none of the mips team uses like rp-pppoe typically gets pushed back. Steve -- gentoo-dev@gentoo.org mailing list