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: Thu, 15 Sep 2022 21:42:26 +0300 Message-ID: <8335cszdgt.fsf@gnu.org> References: <83h718zszj.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18559"; 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 Thu Sep 15 20:43:51 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 1oYtq2-0004he-JF for ged-emacs-devel@m.gmane-mx.org; Thu, 15 Sep 2022 20:43:50 +0200 Original-Received: from localhost ([::1]:55562 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oYtq1-0007dT-GQ for ged-emacs-devel@m.gmane-mx.org; Thu, 15 Sep 2022 14:43:49 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37658) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oYtoo-0006wq-OQ for emacs-devel@gnu.org; Thu, 15 Sep 2022 14:42:34 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:36532) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oYtoo-0003wa-FS; Thu, 15 Sep 2022 14:42:34 -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=rh10RnRDEytSMwsAQf3asQut912KiID7+LMCABOAjY8=; b=al/583yd1E9P DSEht20pSxOA+z7p5rpMa7Z+vgnMIWzBT28ghR6mbZWxEvXeS1zT9TsK6oFXfp++5ha3ubh39XHRI ARnaS4Gd+8g6jF1NOYGdQ9mnnSZYcOJ5IK3qsnLfzA8HtWVmMWcccl4j4AkBEMVHWSUPJ74BnVD12 jP6NZzRtQ/CQZg0gk7HP3O1gOyqIKqpibJmjQWMvi3RnWm8MaNs3nGwkEbhRh6LVAYU2c+ycDqThc nnMirARDERhdNkmIgGWoN4nqoztPmCZMosRfjK10jnNb6znkXPxamBhSYLukHfnt1gaTkBRhZQ13U UEMjcxkXI3RVR/a7q68Ubw==; Original-Received: from [87.69.77.57] (port=2530 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 1oYton-0000Iw-QE; Thu, 15 Sep 2022 14:42:34 -0400 In-Reply-To: (message from Stefan Kangas on Thu, 15 Sep 2022 13:45:31 -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:295444 Archived-At: > From: Stefan Kangas > Date: Thu, 15 Sep 2022 13:45:31 -0400 > Cc: emacs-devel@gnu.org > > >> > Also, how will this HTML version be maintained, after it is produced. > >> > >> The easiest option is to just leave the old generated HTML files alone > >> and update them only if absolutely necessary. > > > > I meant to ask how will we keep them under VCS (CVS in this case). > > I might be missing some context here, because I don't think I understand > what you're asking. Do we need to do anything else besides copying them > in place (to "news/NEWS.NN.Y.html") and running "cvs update"? You need to add it to CVS first and commit, right? My question was would we maintain the HTML NEWS files in CVS together with the rest of the Web pages, or will we do something else? > >> I didn't yet look into this, so I don't know how realistic this is, > >> but I have a hunch that it's doable. Maybe we will only be able to > >> do it for releases newer than Emacs 21 (or something) though. > > > > Do we have links for those older NEWS files on the Web site? If not, > > I see no point in generating NEWS in HTML format for old releases. > > The only benefit I see is that you could then edit the URL to visit the > pages for older releases. I think Karl Fogel pointed out this use case, > and it's definitely something I have done in the past too. The Web site only has announcements going back to v27.1; the versions before that point to an email announcement. So I think there's no reason to have HTML versions of NEWS for versions older than v27.1.