From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id BF165138247 for ; Thu, 16 Jan 2014 01:00:58 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2B45EE0B13; Thu, 16 Jan 2014 01:00:52 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 30EAAE0AD6 for ; Thu, 16 Jan 2014 01:00:51 +0000 (UTC) Received: from [192.168.11.61] (cpe-72-177-217-176.satx.res.rr.com [72.177.217.176]) (using SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: steev) by smtp.gentoo.org (Postfix) with ESMTPSA id 2307F33F5E1 for ; Thu, 16 Jan 2014 01:00:49 +0000 (UTC) Message-ID: <1389833907.20022.7.camel@oswin.hackershack.net> Subject: Re: [gentoo-dev] rfc: revisiting our stabilization policy From: Steev Klimaszewski To: gentoo-dev@lists.gentoo.org Date: Wed, 15 Jan 2014 18:58:27 -0600 In-Reply-To: <20140115190744.GA2645@laptop.home> References: <20140114213719.GA2684@laptop.home> <52D6D489.9030302@gentoo.org> <20140115190744.GA2645@laptop.home> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.5 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-Transfer-Encoding: 7bit X-Archives-Salt: 8d6ffc6d-43fc-43d2-a94b-8bcc038ac8e4 X-Archives-Hash: 23dd4c16bc8cfdbb9cd7e0a2334293fb On Wed, 2014-01-15 at 13:07 -0600, William Hubbs wrote: > When you say "drop keywords" do you mean: > > 1) revert the old version back to ~arch or > 2) remove the old version. > > As a maintainer, I would rather do 2, because I do not want to backport > fixes to the old version. > > William > I'm not sure what he meant by drop keywords either, however, something that I would like to see (with my ARM hat on here) - is, if something is taking a while to stable for a certain arch, remove the keywords except for that existing arch. We actually ran into something along this issue with git. Now, arm is an interesting keyword, because for arm, when something needs to be stabled, we have to test armv4, armv5, armv6, armv6 hardfloat, armv7, armv7 hardfloat, armv7 uclibc. In my testing, one known issue was that git on uclibc did (and still doesn't) work properly starting with git 1.8 - so I noted in the bug that this was the case, and to NOT stable it for arm. Unfortunately, someone else on the ARM team disregarded the note and stabled the new git, then the git maintainers dropped the old versions. Now on arm uclibc, git is entirely broken and unusable. And no, adding more people to the arch team doesn't particularly help, as people are buying more and more armv7 so they test that, but not the rest of the versions - and no one wants to buy the older hardware "because it's so slow" - we know it's slow, that's why it takes time. I'd have definitely preferred that for git, that the 1.7 version stuck around with just KEYWORDS="-* arm" (and maybe even stabling 1.8 but leaving 1.7 in masked?) - I realize it was a bit of a special case because of the new git eclass. Unfortunately, debugging what's going on, is a bit above me, and the only other person I know who can/does work on it, is blueness, and he's quite busy.