Re: Need help creating a test release

[Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>]

On Sun, 2025-04-13 at 12:38 -0400, Eric Cook wrote:
> I wasn't sure what in NEWS needed to be updated, if anything.
> 
> and I am working with the assumption that the next version is 5.10

5.10 seems good, I can't see any reason for a major release at this point
and we're certainly way beyond 5.9.x.

Looks like NEWS has already been updated with some stuff people knew
was going to be interesting --- I think it's again up to people to chip
in with stuff they know about that's not there yet.

As a prod in case anyone needs it, it currently says the following.
Maybe move namerefs and non-forking subsitutions to the top, as
those are more top-level new features than the other stuff?

cheers
pws

Changes since 5.9
-----------------

In region_highlight and zle_highlight, italic and faint can be
specified as font attributes for terminals that support them.

Highlighting groups can be referenced in region_highlight and
zle_highlight for common attribute combinations and a layer can be
specified to indicate precedence where highlighted regions overlap.
Highlighting groups are also supported in the prompt via a new %H
prompt escape.

Ellipsis markers shown by the line editor to indicate where the line
doesn't fit in the terminal can be highlighted.

The ERR_EXIT and ERR_RETURN options were refined to be more self-
consistent and better aligned with the POSIX-2017 specification of
`set -e`. For details on what exactly changed, see the list of
incompatibilities in the README file.

Support for named references and namespaces has been added, similar to
those features in ksh but with some notable differences. The `nameref`
builtin and some ksh-equivalent namespace names are available by loading
the zsh/ksh93 module.  See the documentation of that module for more.

Non-forking command substitutions with ${ ... } and ${| ... } are now
available, and the latter extended with ${|param| ... } to return the
result via assignment to the named param rather than always via $REPLY.