From: Karl Fogel <kfogel@red-bean.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stefankangas@gmail.com, emacs-devel@gnu.org
Subject: Re: Emacs 28.2 released
Date: Wed, 14 Sep 2022 13:49:58 -0500 [thread overview]
Message-ID: <87k065lrjd.fsf@red-bean.com> (raw)
In-Reply-To: <83zgf127oy.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 14 Sep 2022 20:21:17 +0300")
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
next prev parent reply other threads:[~2022-09-14 18:49 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 17:06 Emacs 28.2 released Karl Fogel
2022-09-14 17:21 ` Eli Zaretskii
2022-09-14 18:49 ` Karl Fogel [this message]
2022-09-14 18:56 ` Eli Zaretskii
2022-09-14 19:15 ` Karl Fogel
2022-09-14 19:21 ` Eli Zaretskii
2022-09-14 19:53 ` Karl Fogel
2022-09-15 6:58 ` Eli Zaretskii
2022-09-15 7:44 ` Stefan Kangas
2022-09-15 17:59 ` Karl Fogel
2022-09-14 17:39 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2022-09-12 10:13 Stefan Kangas
2022-09-12 11:28 ` Michael Albinus
2022-09-12 11:55 ` Michael Albinus
2022-09-12 11:59 ` Eli Zaretskii
2022-09-12 12:00 ` Eli Zaretskii
2022-09-12 12:03 ` Michael Albinus
2022-09-12 12:20 ` Lars Ingebrigtsen
2022-09-12 20:59 ` Karl Fogel
2022-09-13 1:36 ` Stefan Kangas
2022-09-13 2:30 ` Eli Zaretskii
2022-09-13 9:39 ` Stefan Kangas
2022-09-13 12:03 ` Eli Zaretskii
2022-09-13 12:46 ` Stefan Kangas
2022-09-13 13:03 ` Lars Ingebrigtsen
2022-09-13 13:43 ` Robert Pluim
2022-09-13 13:55 ` Lars Ingebrigtsen
2022-09-14 16:43 ` Stefan Kangas
2022-09-14 16:47 ` Lars Ingebrigtsen
2022-09-14 17:33 ` Eli Zaretskii
2022-09-14 22:50 ` Stefan Kangas
2022-09-15 5:37 ` Eli Zaretskii
2022-09-15 7:44 ` Stefan Kangas
2022-09-14 16:54 ` Eli Zaretskii
2022-09-14 22:50 ` Stefan Kangas
2022-09-15 5:38 ` Eli Zaretskii
2022-09-14 16:57 ` Karl Fogel
2022-09-14 18:34 ` Bob Rogers
2022-09-16 14:56 ` Stefan Kangas
2022-09-13 15:29 ` Karl Fogel
2022-09-13 15:49 ` Eli Zaretskii
2022-09-13 15:52 ` Eli Zaretskii
2022-09-14 16:59 ` Karl Fogel
2022-09-14 17:04 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k065lrjd.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stefankangas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).