From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Karl Fogel Newsgroups: gmane.emacs.devel Subject: Re: Emacs 28.2 released Date: Wed, 14 Sep 2022 13:49:58 -0500 Message-ID: <87k065lrjd.fsf@red-bean.com> References: <87h719nawm.fsf@red-bean.com> <83zgf127oy.fsf@gnu.org> Reply-To: Karl Fogel Mime-Version: 1.0 Content-Type: text/plain; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10859"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: stefankangas@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Sep 14 20:52:59 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 1oYXVJ-0002YU-Nm for ged-emacs-devel@m.gmane-mx.org; Wed, 14 Sep 2022 20:52:58 +0200 Original-Received: from localhost ([::1]:60748 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oYXVI-0007ls-JV for ged-emacs-devel@m.gmane-mx.org; Wed, 14 Sep 2022 14:52:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52668) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oYXSW-0006pJ-Fq for emacs-devel@gnu.org; Wed, 14 Sep 2022 14:50:04 -0400 Original-Received: from sanpietro.red-bean.com ([45.79.25.59]:34356) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oYXST-0008ML-DW; Wed, 14 Sep 2022 14:50:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=red-bean.com; s=202005newsp; h=Content-Type:MIME-Version:Message-ID:Date: Reply-To:References:In-Reply-To:Subject:Cc:To:From:Sender: Content-Transfer-Encoding:Content-ID:Content-Description; bh=BqlIXU5uZeB2gSNzfQJkBWi5wEH2hu1CSUGHMvQQBMU=; t=1663181400; x=1664391000; b=d4W682eEuAzmMDMcFzoXjzbYXZg3FHNel3HWUI/Xn6Q5JWwpd9wM4B3H0LTWQHFdOQlFY0e+ewS y/HfYNEkE+CkTUtekKUA0CSloSy/n+k/3CtAv4PEm1SaUI3TNSPH4wlRSy/lMyW8EOFCZckhcF9ix G+uU5qhdeKeoQWbldOPmb8BxYwQiDLxmFWMfKqa3KcEeJWsqz7EKeYdhlihDQ0FA3C5JZXydpoZ4P 7PsCkmfKfVT9wSR1DjEBFf/CBcEJcO/ZiHr3P4XczBTxYrllRxop/eYfkGFPTCMaMiPH++oXWc+Mn wNI0VUZrMkVnuXSRTrJT9uZEnCSB/Vd10gzw==; Original-Received: from [12.106.183.66] (port=1990 helo=hummy) by sanpietro.red-bean.com with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1oYXSR-00BFSs-6Y; Wed, 14 Sep 2022 18:49:59 +0000 In-Reply-To: <83zgf127oy.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 14 Sep 2022 20:21:17 +0300") Received-SPF: pass client-ip=45.79.25.59; envelope-from=kfogel@red-bean.com; helo=sanpietro.red-bean.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action 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:295358 Archived-At: I think I see where the miscommunication is coming from here. Let me explain my suggestion more clearly: Stefan's announcement mail was for 28.2, and has this sentence: "Emacs 28.2 is a bug-fix release, with no new features with respect to Emacs 28.1." That's probably why his email didn't have any link out to a description of the release -- because 28.2 has no new features; it's just bugfixes. (You can see his mail here, for reference: https://mail.gnu.org/archive/html/emacs-devel/2022-09/msg00730.html) What I'm saying is that *every* release announcement email should have a clickable link to the release notes for that release, even when we're only making a bugfix release. There are a couple of reasons for this, one direct and one more subtle: The direct reason is: Many readers will want to be able to click on a link to see what's in the release, because even if it's only bugfixes, they'll want to know what those fixes were. They're making a decision about whether to upgrade, and typically that decision involves reading the release notes. So if we just point to the release notes for *every* release, always, we'll help smooth their decision process. The more subtle reason is: Some people who (for whatever reason) didn't upgrade from >= 27.x when 28.1 came out may decide to do so when they see the 28.2 announcement. Online release notes are usually structured so that if one is reading the notes for X.Y, it's very easy to get from there to the notes for X.(Y-1) -- you just scroll farther down in the web page, or you edit the URL in some obvious way, or something like that. Thus, people who saw Stefan's announcement would have the following assumption in the back of their minds: "If I can get to the release notes for 28.2, it'll be an equally easy hop from there to the release notes for 28.1". Therefore, including a link to the 28.2 release notes in the 28.2 announcement email would help those who are upgrading from >= 27.x too, as well as those upgrading from 28.1. So my suggestion is that release announcement emails always include a direct link to the release notes for that release, for the reasons given above. And specifically, that we stick to this policy even for minor or bugfix releases. I hope this clarifies. Best regards, -Karl