Follow-up Comment #15, bug #62916 (group groff): Hi Dave,
At 2025-07-22T20:48:18-0400, Dave wrote:
> Follow-up Comment #14, bug #62916 (group groff):
>
> In my mental conception, "NEWS" lists changes already made in the
> current release, and the list proposed in this ticket would list
> changes being considered for a future release, as a heads-up to users
> who may depend on current behavior (and who may want to discuss a
> proposed change affecting them).
That makes sense to me.
> Perhaps I was never explicit about this purpose, so perhaps your
> mental model differs.
>
> But based on my model, the bug #67329 change seems worth noting as a
> future incompatible change.
I think our only difference is that I regard "deprecations" as a proper
subset of incompatible changes. Here's an example of an incompatible
change that is not a deprecation.
NEWS:
* GNU troff no longer accepts a newline as a delimiter for the
parameterized escape sequences `\A`, `\b`, `\o`, `\w`, `\X`, and
`\Z`.
Not sure it's worth proliferating more tickets for this distinction.
Should we retitle this ticket to "incompatible changes under
consideration for groff 1.25"?
I'd propose we not leave the ticket open in perpetuity, as it could
accumulate a lot of comments as sundry ideas are mooted and discarded.
Regards,
Branden
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?62916>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
