From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs 28.2 released Date: Wed, 14 Sep 2022 22:21:45 +0300 Message-ID: <83h7192246.fsf@gnu.org> References: <87h719nawm.fsf@red-bean.com> <83zgf127oy.fsf@gnu.org> <87k065lrjd.fsf@red-bean.com> <83illp239n.fsf@gnu.org> <87leqlkbsh.fsf@red-bean.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39979"; mail-complaints-to="usenet@ciao.gmane.io" Cc: stefankangas@gmail.com, emacs-devel@gnu.org To: Karl Fogel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Sep 14 21:23:00 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oYXyO-000ABz-Mu for ged-emacs-devel@m.gmane-mx.org; Wed, 14 Sep 2022 21:23:00 +0200 Original-Received: from localhost ([::1]:59672 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oYXyN-0005wu-O3 for ged-emacs-devel@m.gmane-mx.org; Wed, 14 Sep 2022 15:22:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43186) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oYXxM-0004UU-Uy for emacs-devel@gnu.org; Wed, 14 Sep 2022 15:21:58 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:48920) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oYXxM-0005Fu-My; Wed, 14 Sep 2022 15:21:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=LFwnrraWAbJLtklZCkyDjdxgrVnGuwrJR7KHvvZq8KY=; b=n/C+s1JUmD5J jwgRI8i0yAgTxhOEZY0urhU1a/TEl2p5LbZzRNizuciXXfNQcGEbJ3EaXqmSdtURBh9uOiRzCaSrV FZeIsYe0+VKmDTC3UVqnwSLwKQ0mAUTavV6ENMUIwspvLiq1lXRGHN2JF7+C5d2osk8DUzH5EG17M cPWN28QzS37N642Q18fMP6SB66Q0bqQLK1yH1T3VqvnJu2CDpzrTrDhgfI6bX918p0sP4jaXERdlr 52o41HrV0aBZBNwCYoOqxVz9cnNb/RkGqFo9QFU0b5D/9iSrtr1Ayg6g3H/Nbmw/9DxRIxbaY+/dD nyC3uYzzHfiHaBygKI8Wbg==; Original-Received: from [87.69.77.57] (port=3231 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oYXxL-0002k9-7g; Wed, 14 Sep 2022 15:21:56 -0400 In-Reply-To: <87leqlkbsh.fsf@red-bean.com> (message from Karl Fogel on Wed, 14 Sep 2022 14:15:26 -0500) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:295361 Archived-At: > From: Karl Fogel > Cc: stefankangas@gmail.com, emacs-devel@gnu.org > Date: Wed, 14 Sep 2022 14:15:26 -0500 > > On 14 Sep 2022, Eli Zaretskii wrote: > >But we don't have any release notes for bugfix releases. We > >don't > >track bugs that we fix in such releases, and don't record them > >anywhere except in Git logs. We certainly don't record them in > >NEWS, > >which is why what Stefan did misses your point. > > We have an entry in NEWS for 28.2. > > That entry has a substantive item about an installation change. > There are also a couple of items listed under "Changes in > Specialized Modes and Packages in Emacs 28.2" (although one of > them says that the change was actually released in 28.1 and that > we just forgot to include it in the release notes then). These are not the bugfixes whose list you wanted to see. > People who land on the 28.2 notes can easily find their way from > there to the previous notes, and so on. Since we don't know the > version of Emacs the reader might be contemplating upgrading from, > by linking from the announcement email to the corresponding recent > release notes, we put the reader at a starting point from which > they can easily trace back as far as they need to go to make their > decision. > > In other words, *even* if all we do for a minor release is put an > entry into NEWS that says... > > > * Changes in Emacs X.Y > > > > This is a bug-fix release with no new features. > > ...and then we point to that (in whatever form it lives on the > web), we are still helping the reader start their informational > journey. You keep changing the request on every step. It is very hard to have a useful discussion this way. So now I understand that you suggest having something like this: . a link to NEWS of the current release (for minor releases, this NEWS could be empty or almost empty, and we don't have a way to describe the bugs we fixed there, but you now say this is not important?) . a link to the announcement of previous release, where there will be a link to NEWS of that release . and so on, all the way to some old enough release beyond which no one will bother Is that correct? Or do we have a misunderstanding again?