From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2233 invoked by alias); 17 May 2017 18:21:14 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 653 invoked by uid 89); 17 May 2017 18:21:13 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=81, 8.1, assess, announcement X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 17 May 2017 18:21:12 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id D3A1339BB8; Wed, 17 May 2017 14:21:13 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id icShv1FzzGJA; Wed, 17 May 2017 14:21:13 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 8FBFC39BB7; Wed, 17 May 2017 14:21:13 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 0D9B38031E; Wed, 17 May 2017 11:21:11 -0700 (PDT) Date: Wed, 17 May 2017 18:21:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: Yao Qi , gdb-patches@sourceware.org Subject: Re: GDB 7.99.91 MinGW compilation warning in tui.c Message-ID: <20170517182111.loklx3ex64f5brco@adacore.com> References: <20170504194442.63AAF60B72@joel.gnat.com> <83mvancrze.fsf@gnu.org> <83r2zt89c8.fsf@gnu.org> <86k25f8n5w.fsf@gmail.com> <83a86b5t6f.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83a86b5t6f.fsf@gnu.org> User-Agent: NeoMutt/20170113 (1.7.2) X-SW-Source: 2017-05/txt/msg00405.txt.bz2 > > Did you push it to 8.0 branch? I think we need it in 8.0 branch. > > I pushed it to master. Is it really serious enough to have a Bugzilla > report for it, have it listed on the wiki, etc.? You only need that for the .1 (or any later release on that branch). For the .0, it's OK to just push to the branch without any of the above. Just to provide a reminder for those who haven't seen why we have this procedure in place: It's to give users a way to assess the fixes that were introduced between two minor releases on a given branch. Eg: I have 8.0 installed on my machine, and today 8.1 just came out; is there any point in me upgrading? For that, I would look at the announcement, which would list all the PRs that were part of this corrective release, look at the PRs that looks potentially interesting, and would then be in a better position to decide. It also helps me (as release manager) automatically generate the announcement for the .1, making sure I don't miss some changes by accident. For the .0, it's a major release, so the information we provide about the release is coarser. I normally write a summary of the NEWS file with a reference to it for more information. Also, several contributors still decide that it's worth creating PRs and then set the milestone to the correct release once fixed. This gives more information about the specific problems they fixed. But that part is optional at this point. -- Joel