From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id CF8AF3858D28 for ; Mon, 1 May 2023 13:37:29 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org CF8AF3858D28 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=simark.ca Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=simark.ca Received: from [10.0.0.170] (unknown [167.248.160.41]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id F1B731E0D6; Mon, 1 May 2023 09:37:28 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=simark.ca; s=mail; t=1682948249; bh=IXhYMMSehEdXQ1FCSW+JGmXQWdX6VZvrzUuLcBKVyBo=; h=Date:Subject:To:References:From:In-Reply-To:From; b=EDUyp7vLZgcOhZ8JRMUfM21Km/F3yRAaVa/MXOxG9geh9oLWCCHOm45WEMIIj70/w ctA7IxuOhgHxYYa47y/nGn7uECehfjXa5NZ1fS+Bd05Y6XNPEcc2a5wAJxNGVq83yx i/FGVUvL9U7ErLflt6bxlqFDDmZ8c5a6+3rX6/Fc= Message-ID: <945cb511-3bd0-7004-caa7-9f0deb76e766@simark.ca> Date: Mon, 1 May 2023 09:37:28 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 Subject: Re: GDB 13.2 and GDB 14 releases... Content-Language: fr To: Joel Brobecker , gdb-patches@sourceware.org References: From: Simon Marchi In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,SPF_HELO_PASS,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 4/29/23 16:15, Joel Brobecker via Gdb-patches wrote: > GDB 14.1 Branching and Release > ============================== > > Normally, my default approach is to start talking about the next > major release as soon as the previous .2 release is out. The idea > is to give ourselve 3 months or so to prepare for it, branch and > then release, so as to try to follow a schedule of one major release > every 6 months. > > In this case, I think it's too early to tell. I've looked at the NEWS > file, and while there are a number of nice new features, maybe we might > want to wait a little longer to see if we can pack this release a little > more. IMO, it's better to make regular releases than waiting to have a certain amount of changes. The changes currently in master might not look important to me, but maybe someone else is eagerly waiting for a specific fix or feature to be officially released. Simon