From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 41872 invoked by alias); 26 Mar 2019 20:40:48 -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 41782 invoked by uid 89); 26 Mar 2019 20:40:47 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Languages-Length:623 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; Tue, 26 Mar 2019 20:40:46 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 6B6EF116CDC; Tue, 26 Mar 2019 16:40:44 -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 NAPSnhj-PXpQ; Tue, 26 Mar 2019 16:40:44 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 3C363116CD9; Tue, 26 Mar 2019 16:40:44 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 9102583AE0; Tue, 26 Mar 2019 13:40:42 -0700 (PDT) Date: Tue, 26 Mar 2019 20:40:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: gdb-patches@sourceware.org Subject: Re: GDB 8.3 release update (2019-03-25) Message-ID: <20190326204042.GA6837@adacore.com> References: <20190325204307.GA21459@adacore.com> <83d0men0ei.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83d0men0ei.fsf@gnu.org> User-Agent: Mutt/1.9.4 (2018-02-28) X-SW-Source: 2019-03/txt/msg00608.txt.bz2 > > If we can confirm there aren't any issues we know of that we want > > to fix for 8.3, I could create the release, say, this weekend, or > > early next week. > > All the problems I knew about are fixed, but I wonder whether we need > another pretest, since so many non-trivial changes went in. Yeah, I saw those, and unfortunately saw them too late to raise a flag. Since they are in, now, might as well keep them. I can create another pre-release -- but I'll wait for the various issues identified before doing so. Might as well include those in the next pre-release. -- Joel