emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs 28.2 released


From: Eli Zaretskii
Subject: Re: Emacs 28.2 released
Date: Wed, 14 Sep 2022 20:21:17 +0300

> From: Karl Fogel <kfogel@red-bean.com>
> Cc: stefankangas@gmail.com,  emacs-devel@gnu.org
> Date: Wed, 14 Sep 2022 12:06:17 -0500
> 
> >I was not suggesting including the contents of the NEWS file.  I 
> >was
> >suggesting including a *link to* the NEWS file, so that those who 
> >are
> >interested can follow the link.
> 
> I should have said: "a link to the NEWS file or some other web 
> page that describes the release".

But we already do that!  For a major release, the Web page includes
its main new features, and the Web page mentions them for a month
since the release.  And the announcement tells how to read the NEWS
file.  What is missing?

> The key point is for the announcement email to link to a more 
> detailed description of what's new in the release.

More detailed than what?

> Whether that description is the NEWS file or something else is a
> separate question -- whatever it is, it'll have more information
> about the release than the email announcement has.

Here's the list of main new features in Emacs 28.1, copied from
https://www.gnu.org/software/emacs/

  Emacs 28.1
  Released Apr 4, 2022

  Emacs 28.1 has a wide variety of new features, including:

      Native compilation of Lisp files
      Text shaping with HarfBuzz and drawing with Cairo
      Support for loading Secure Computing filters
      Much improved display of Emoji and Emoji sequences
      New system for documenting groups of functions
      A minor mode for context menus
      Mode-specific commands
      Emacs shows matching parentheses by default
      Many improvements and extensions to project.el

There's a link to NEWS for people who want that.

What is the problem for the email announcement to have the same list
of main new features, and refer to NEWS, as we already do, for those
who really want that?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]