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 569721381F3 for ; Sun, 15 Sep 2013 19:03:51 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D7D42E0CB0; Sun, 15 Sep 2013 19:03:50 +0000 (UTC) Received: from mail-vb0-f52.google.com (mail-vb0-f52.google.com [209.85.212.52]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 3EA64E0C19 for ; Sun, 15 Sep 2013 19:03:50 +0000 (UTC) Received: by mail-vb0-f52.google.com with SMTP id f12so2309033vbg.11 for ; Sun, 15 Sep 2013 12:03:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=86TUxUeP2mfi9i48R48cU0uFmHwuNEbsxQ8pkpAYaBg=; b=tL1a9rjcNAlNZcQ9H9IDrKuw2zdOgtInzpnU8CEEZRGQNyv/9x50JkTZt0R+kb7exN 2ya5i9yaT9n6I5HMxQql0p4dilqUMrArSAdXxx/PyvxhxQluxugmX9jp/k8cEtx8T6HJ duYdlXsJGps0GnBnOCLjBx8zlW4mqDSibh1JVQjZM9XOyuq2gK5DS506eFff8FAzFSQE iNa4bo0/KSq7P3wAiFmadGPvbU+w+SDjlgkmNfk3UGgSOHm1yV3NbrmVa8ZGtzXhTDYM TT79fuUwu/YsdyPkr4rDYcs4idpZJevSyNQ+S9prdz9/rFARHXckU6/1IdrCCp9sOXqv Bo2Q== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.52.64.143 with SMTP id o15mr19526564vds.16.1379271829431; Sun, 15 Sep 2013 12:03:49 -0700 (PDT) Sender: freemanrich@gmail.com Received: by 10.52.187.68 with HTTP; Sun, 15 Sep 2013 12:03:49 -0700 (PDT) In-Reply-To: <1379258522.8240.3.camel@localhost> References: <21020.30575.805569.383992@a1i15.kph.uni-mainz.de> <20130829152248.GA3432@shimane.bonyari.local> <1377796652.5477.15.camel@localhost> <1379258522.8240.3.camel@localhost> Date: Sun, 15 Sep 2013 15:03:49 -0400 X-Google-Sender-Auth: 3Y65_ehutot8y43nhFxidq7-5mU Message-ID: Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2013-09-10 From: Rich Freeman To: gentoo-project@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 7a8059be-b638-4326-9974-b5f3a681e527 X-Archives-Hash: 59ec312afea42d7b78b3612afb6601b9 On Sun, Sep 15, 2013 at 11:22 AM, Pacho Ramos wrote: > El dom, 15-09-2013 a las 11:03 -0400, Rich Freeman escribi=F3: >> >> So, how about this as a policy: >> If a maintainer has an open STABLEREQ, or a KEYWORDREQ blocking a >> pending STABLEREQ, for 90 days with archs CCed and otherwise ready to >> be stabilized, the maintainer can remove older stable versions of the >> package at their discretion. A package is considered ready to be >> stabilized if it has been in the tree for 30 days, and has no known >> major flaws on arches that upstream considers supported. >> >> Note that if upstream doesn't support an arch, then it falls to the >> arch team (and not the maintainer) to support that arch if they want >> it stable. >> > I guess an important problem is that, once we drop keywords in a > package, a cascade effect can appear. For example, if we drop stable > keywords of gtk+ and pango due pending keywording, we will need to also > drop a ton of packages. And for cases where we would need to drop the > keywording completely, the situation can be even more difficult. Fully appreciate that. Given the choice of removing ALL of the stable keywords, and removing many of the keywords, the latter seems to be a better choice, at least initially. However, I do see that as a PITA. If it becomes a trend, the stable keywords should be dropped entirely. Really, it should be the arch teams themselves that step up and remove their own stable keywords. For this reason I'm not sure I'd even want to require maintainers to change any keywords when they remove the last stable version on an arch - just let the reverse dependencies break and either the arch team or users will have to clean up the mess (which nobody will see unless they use that arch). Ultimately, arch teams need to step up if they want to have stable keywords= . As far as the users go - more need to become developers if they want to have stable keywords, or pay somebody else to do so on their behalf. That's just how things work in a volunteer-based distro. Rich