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 EE4C31396D9 for ; Wed, 11 Oct 2017 03:56:54 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E84C12BC026; Wed, 11 Oct 2017 03:56:46 +0000 (UTC) Received: from blaine.gmane.org (unknown [195.159.176.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 907F9E084E for ; Wed, 11 Oct 2017 03:56:46 +0000 (UTC) Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1e288J-0002px-BA for gentoo-dev@lists.gentoo.org; Wed, 11 Oct 2017 05:56:35 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-dev] Re: RFC v2: news item for the 17.0 profiles Date: Wed, 11 Oct 2017 03:56:30 +0000 (UTC) Message-ID: References: <1528131.eIYCIZq90I@pinacolada> <1537421.UsZouyEjHW@pinacolada> 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=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@blaine.gmane.org User-Agent: Pan/0.143 (Quaint little villages here and there; 54f7ff4db) X-Archives-Salt: 7fd1c0a8-181f-4eee-b671-55c5c8497f9a X-Archives-Hash: 0947733c6b6c0a662cfa4f9b368e6979 Alec Warner posted on Tue, 10 Oct 2017 15:28:41 -0400 as excerpted: >> Please consider switching from your current 13.0 profile to the >> corresponding 17.0 profile soon after GCC 6.4.0 has been stabilized on >> your architecture. The 13.0 profiles will be deprecated and removed in >> the near future. >> >> > Can you commit to a deadline on this? > > Its OK to be wrong (e.g. say 1 month but remove in 3); but "near future" > is not actionable by readers. Will the 13.0 profiles be removed all together, or per-arch? If they're removed all at the same time, then the time-limiting factor will certainly be how long it takes the last arch to stabilize gcc-6.4+, something that's likely not entirely predictable but that might take some time, given gentoo's known issues with straggling archs. If the existing profiles will be deprecated and removed per-arch, with some fixed time after gcc-6.4+ stabilizes on that arch as a goal, then the time for most popular and best maintained archs may be predicted now, but the time will differ for each one, so the best that could be done would be either a time range or a list of the known ones, with presently unknowns being added to the list in further revisions of the news item. The other alternative might be to word it something like (1 year can be 6 months or whatever instead, if that works better): "13.0 profiles are set to be removed one year after the last arch stabilizes gcc-6.4+, with the goal for the gcc stabilization being the end of 2017, meaning 13.0 profile removal is planned for the end of 2018 if all archs meet their gcc-6.4+ stabilization goal." -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman