Re: Emacs 28.2 released

[Eli Zaretskii]

> From: Karl Fogel <kfogel@red-bean.com>
> Cc: stefankangas@gmail.com,  emacs-devel@gnu.org
> Date: Wed, 14 Sep 2022 14:15:26 -0500
> 
> On 14 Sep 2022, Eli Zaretskii wrote:
> >But we don't have any release notes for bugfix releases.  We 
> >don't
> >track bugs that we fix in such releases, and don't record them
> >anywhere except in Git logs.  We certainly don't record them in 
> >NEWS,
> >which is why what Stefan did misses your point.
> 
> We have an entry in NEWS for 28.2.
> 
> That entry has a substantive item about an installation change. 
> There are also a couple of items listed under "Changes in 
> Specialized Modes and Packages in Emacs 28.2" (although one of 
> them says that the change was actually released in 28.1 and that 
> we just forgot to include it in the release notes then).

These are not the bugfixes whose list you wanted to see.

> People who land on the 28.2 notes can easily find their way from 
> there to the previous notes, and so on.  Since we don't know the 
> version of Emacs the reader might be contemplating upgrading from, 
> by linking from the announcement email to the corresponding recent 
> release notes, we put the reader at a starting point from which 
> they can easily trace back as far as they need to go to make their 
> decision.
> 
> In other words, *even* if all we do for a minor release is put an 
> entry into NEWS that says...
> 
> > * Changes in Emacs X.Y
> > 
> > This is a bug-fix release with no new features.
> 
> ...and then we point to that (in whatever form it lives on the 
> web), we are still helping the reader start their informational 
> journey.

You keep changing the request on every step.  It is very hard to have
a useful discussion this way.

So now I understand that you suggest having something like this:

  . a link to NEWS of the current release (for minor releases, this
    NEWS could be empty or almost empty, and we don't have a way to
    describe the bugs we fixed there, but you now say this is not
    important?)
  . a link to the announcement of previous release, where there will
    be a link to NEWS of that release
  . and so on, all the way to some old enough release beyond which no
    one will bother

Is that correct?  Or do we have a misunderstanding again?