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: Generate NEWS.XX.Y.html file for Emacs website Date: Sun, 18 Sep 2022 08:22:01 +0300 Message-ID: <83r109z286.fsf@gnu.org> References: <83v8plzuoi.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31264"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Sep 18 07:23:26 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 1oZmm6-0007yn-Go for ged-emacs-devel@m.gmane-mx.org; Sun, 18 Sep 2022 07:23:26 +0200 Original-Received: from localhost ([::1]:44372 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oZmm4-00074X-T3 for ged-emacs-devel@m.gmane-mx.org; Sun, 18 Sep 2022 01:23:24 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47914) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oZmki-00068g-Us for emacs-devel@gnu.org; Sun, 18 Sep 2022 01:22:00 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:46498) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oZmki-0002iN-KH; Sun, 18 Sep 2022 01:22:00 -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=t5qNmpnQPPj/sj76Sc2Q+jKBF91MfLjARtQv3h51kxQ=; b=gQLmD5HrZ53N X/QZmMSuyXvLJRPxuDGzXZtCb30Gv9lSYUJyQyOm6VTZoZeniI2Eo6Ymut/Gny/67s/5bJDjrxaoE 3O8m07e6Q8hVUajP0lk5xeLVhsMjkfedwjpzGCMnbHbYnnDTS4xzyDX1gbMvID3DEiStNQATRewHt upE54wTOjCra2pzNcAwx5Jh0mN17+mA1kD55G+3MgS4DUr2loOORQVgaGkIkaKTPvd8ZrlA1JFdrn 2VeHlQCDxVL7k/HUt0TnQQw70c4EBfcLcQEw+Fx+YlhMGWvoL0rlh0Lc3Gunvpy0XAm940GsMzfaa XXgIAHyPO3uYrPG00H6VJw==; Original-Received: from [87.69.77.57] (port=2118 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 1oZmki-000270-0j; Sun, 18 Sep 2022 01:22:00 -0400 In-Reply-To: (message from Stefan Kangas on Sat, 17 Sep 2022 16:08:07 -0400) 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:295556 Archived-At: > From: Stefan Kangas > Date: Sat, 17 Sep 2022 16:08:07 -0400 > Cc: emacs-devel@gnu.org > > Eli Zaretskii writes: > > > It still included NEWS for Emacs 28.1. I thought we wanted to delete > > those, leaving just the news of the single release? > > The idea came up to just have a single page per major version, which > incidentally simplified generating the files. (I was particularly happy > about the latter.) I understand, but I don't think it's TRT. At the very least there should be a prominent separator between the current release and the previous ones, because it's all too easy to mistakenly go to those older sections thinking they belong to the current release. See, this is exactly why I said from the get-go that we should only have NEWS for major releases -- that we will show the humongous NEWS for minor releases (because it's easy), and people will get confused. > That's why I added the headlines for the versions, and also anchors so > we would link to: > > https://www.gnu.org/software/emacs/news/NEWS.28.html#28.1 > https://www.gnu.org/software/emacs/news/NEWS.28.html#28.2 I only know that I quickly found myself crossing the line. And I'm supposed to know this file almost by heart. > > Also, is it possible not to number the items? The Emacs 28.2 NEWS are > > short, so it doesn't matter much, but for a major release the numbers > > get to ridiculous values, IMO. Moreover, people will start reporting > > issues referencing these numbers, and we will have to reverse-engineer > > them back to NEWS items. > > I think we can remove the numbers. I only kept them because it felt > easier to navigate such a large file with them, but I'm happy either way. > > (The change would just be one liner to the org header.) Thanks, let's do it, then. > > Get ready for bug reports... > > Of course. No good deed goes unpunished. ;-) None whatsoever.