From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 21C71139694 for ; Tue, 11 Jul 2017 13:06:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B9D4A2740E1; Tue, 11 Jul 2017 13:06:38 +0000 (UTC) Received: from mail-yb0-x242.google.com (mail-yb0-x242.google.com [IPv6:2607:f8b0:4002:c09::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 6CF82234087 for ; Tue, 11 Jul 2017 13:06:38 +0000 (UTC) Received: by mail-yb0-x242.google.com with SMTP id n205so5465161yba.1 for ; Tue, 11 Jul 2017 06:06:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=QdPidQZ7UIPoeqjjzSRX1fXr4RPT/DaMENFf/MKZo7w=; b=tcivxIfq4cqBJZhE0u0JBvDMZO1PxO0IgipGQqgMvXWvdoMQzlXZVK3rf31rGTCUJ/ 7ZqRRaCYb0+zIJqC5bgKTXNrkLQ8+7PWNpbrIeZWZGbYWX953pEHp0IvE8Lx1Ulj1pFD hZ3PzZGvjc1QjZhKgX/5C72xWqdz2TC0ezAyyWDqIbFPMqy7tgki/oyHFugRoxoKtxTP LHeIexThc642KXz3AxpmfthHU3O5twOPsjtxgSQ0P8oL+NhVPMK0XHvKVopK59QjfSZE X4zpu7/oY0TmK1TPCgzuDnqfIbPHP0w0cFE66lt7HOvinhCKP1hXgjqRRD4+zLwfc55D KPZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=QdPidQZ7UIPoeqjjzSRX1fXr4RPT/DaMENFf/MKZo7w=; b=l8RX9/5yTiLJo8hGhq8jBYpgU6XUxxea0r52sLYh5OF2LLtiotNF7ZWHMSoNdlZnVf J6SaYHu47qofctSC2IltxmyDTjJXKoaZHWtrGjUIcpWBWobhgSSUFAkJtJHR2Ph2Ll7i o4v2jfJyBqKn8mCaUp9UTzVsDjotUr9+EjuBUnGS/qynkTU9N2XGydT7QBJiX5+GGQ9c CcXsv7A1pJzd3a//xI1Y2KS+BMt/VJzjhVhXXOUxvcrCANGg7u6jBxoM0V8Q5uN8kBO6 ltwE1aSLk+0vf9QXtb7kkLMBQvA5TNoAfvDvfnFNiU0k92OpQ0OoEs9Sdf3Xu8oFpZ9y cLMA== X-Gm-Message-State: AIVw113jc7TtTIDXiYWHGZX7CN9EKtzMGd+FE4sGMQn+AhjU3ktX28YA Uk93QnyLTv+CLYZ0OIZPZ7jlqWR+Q3Gs X-Received: by 10.37.161.227 with SMTP id a90mr18303151ybi.128.1499778397233; Tue, 11 Jul 2017 06:06:37 -0700 (PDT) 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 Sender: freemanrich@gmail.com Received: by 10.129.115.212 with HTTP; Tue, 11 Jul 2017 06:06:36 -0700 (PDT) In-Reply-To: <0cb79760-99bd-9b95-8771-23af851e71c3@gentoo.org> References: <1897557.6sYsMVzEX5@wanheda> <20170710225725.4c85c26a4f89fe53686f2fb2@gentoo.org> <20170711022906.39a6a2bfd78fb8e6f5f61b6f@gentoo.org> <0cb79760-99bd-9b95-8771-23af851e71c3@gentoo.org> From: Rich Freeman Date: Tue, 11 Jul 2017 09:06:36 -0400 X-Google-Sender-Auth: 1Y01vHJAw1_JVqfh_k5RwnJZ6Rk Message-ID: Subject: Re: [gentoo-dev] Re: taking a break from arches stabilization To: gentoo-dev Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 18dee88d-dbe3-4906-9fd7-720e5a3f423b X-Archives-Hash: a3b37649305a47e18b7637bc6214ccb9 On Tue, Jul 11, 2017 at 8:59 AM, Michael Palimaka wrote: > On 07/11/2017 09:29 AM, Andrew Savchenko wrote: >> >> Even if such stabilization is allowed, there are unanswered >> questions here: >> - is following seciton 4.1 from wg recommendations is sufficient? >> - should developer test each stabilization candidate on an >> up-to-date stable setup? > > The guidelines from that document are ripped straight out of the > devmanual and are a good starting point but rather generic. You can find > some more detailed suggestions on things to consider while testing on > the wiki: https://wiki.gentoo.org/wiki/Package_testing > I think that in practice arch teams don't do have the stuff on that wiki page. Maybe some people do, but back when I was an amd64 AT I don't think anybody went testing multiple USE combinations for a typical package. However, to directly answer one of Andrew's questions, yes, you definitely should test on a stable system/chroot/container. I've seen a few package updates over the years that wouldn't even build and it was probably because whoever keyworded it never even tried building it with stable dependencies. That is pretty rare though. -- Rich