From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19265 invoked by alias); 7 Feb 2018 03:32:51 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 19251 invoked by uid 89); 7 Feb 2018 03:32:51 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=grade, quality 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, 07 Feb 2018 03:32:49 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 05CD756271; Tue, 6 Feb 2018 22:32:48 -0500 (EST) 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 THvavGluuQ9s; Tue, 6 Feb 2018 22:32:47 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 9CD565626F; Tue, 6 Feb 2018 22:32:46 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 502818304F; Wed, 7 Feb 2018 07:32:42 +0400 (+04) Date: Wed, 07 Feb 2018 03:32:00 -0000 From: Joel Brobecker To: Simon Marchi Cc: Dennis Clarke , gdb@sourceware.org Subject: Re: Stop updating ChangeLog? Message-ID: <20180207033242.kcakjc3yh3xtooop@adacore.com> References: <20180206073354.juuhsw4q7tzi74w2@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) X-SW-Source: 2018-02/txt/msg00050.txt.bz2 > > SUMMARY : ChangeLog is part of the quality statement for a given > > production release I do not agree with that statement if made in a general context. As you can see from Simon's answer, the notion of ChangeLog is not universal, and the purpose they serve can change between project, and therefore not serve the goal you are looking for. Whether a project is beta or not is something the project will tell you. A list of changes cannot tell you that. At best, it can tell you how active the project is or not. > > I see work happening all the > > time inside the Curl/libCurl project and Daniel Stenberg is quite active > > and reasonable about checking with people on the state of bugs before a > > move to a "release" or a "stable" version dropped on the world. Considering that this is mostly standard practice, I don't understand the point your are trying to make. The GDB contributors work together with the release manager to ensure that we create high quality releases. ChangeLogs have nothing to do with that process. > > Remove the ChangeLog from the "production" grade "release" and > > I would ask what do you replace that information with? It depends what users are looking for: If they are interested in the list of changes, they clone the git repository, and access it from there. If they are wondering whether a bug if fixed or not, then they can look at the bugzilla database first. If no information is found there, then just try the latest. -- Joel