Follow-up Comment #13, bug #62916 (group groff): [comment #12 comment #12:] > Bug #67329 is not strictly seeking to deprecate anything, but if the list > topic is generalized from "things to deprecate" to "back-incompatible changes > groff is considering," it would qualify.
In principle it's not necessary to list things that aren't deprecations here;
they'd belong to Item Group "Feature Change" by definition, which should
therefore prompt me (or a future maintainer) to compose a "NEWS" file entry
for the change, and that in turn should force consideration of whether the
feature change would impact the rendering of existing documents.
Which isn't to say I mind bug #67329 being noted here--I simply wanted to
explain my maintainerly notions of bug triage and management.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?62916>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
