From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15770 invoked by alias); 18 Aug 2012 16:19:51 -0000 Received: (qmail 15762 invoked by uid 22791); 18 Aug 2012 16:19:50 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_NO X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 18 Aug 2012 16:19:34 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 8BE9B1C7948; Sat, 18 Aug 2012 12:19:33 -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 a6kGj4RQKiiS; Sat, 18 Aug 2012 12:19:33 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 452D91C7946; Sat, 18 Aug 2012 12:19:33 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 7DE5014561A; Sat, 18 Aug 2012 09:19:25 -0700 (PDT) Date: Sat, 18 Aug 2012 16:19:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: Jan Kratochvil , gdb-patches@sourceware.org Subject: Re: GDB 7.5: Problems with the auto-load safe-path feature Message-ID: <20120818161925.GJ2798@adacore.com> References: <83d32ogz3g.fsf@gnu.org> <20120818132128.GA6431@host2.jankratochvil.net> <838vdcgs7c.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <838vdcgs7c.fsf@gnu.org> User-Agent: Mutt/1.5.20 (2009-06-14) 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 X-SW-Source: 2012-08/txt/msg00512.txt.bz2 > > BTW sorry for this note but 7.5 had a long pre-release time to catch these > > issues you are reporting. > > There's a limit to how many projects one can pretest, and still do > something useful during the day (assuming GDB maintenance is not what > you get your paycheck for). I think that's a fair comment. On the other hand, there are always going to be things tested by others that you might disagree with, as is the case here. In any case, we have the option of making a minor/corrective release, if it makes sense. > I'm open to ideas how to help make our pre-release testing better I usually make pre-release packages and then wait for a minimum of 2 weeks before producing the official release. If you'd like, you can build and install them the same way you would for the first release. If all goes well, the first official release could be your first corrective release... -- Joel