Re: Structured Changelogs for ELPA packages

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > - The strict approach would be to say that if we want packages to have
  >   fine-granular news, that they have to use a specific file format, say
  >   Org-mode and that the sections describing specific releases have to be
  >   annotated with tags or properties.

Org mode isn't an Emacs standard for files which contain items.
It is a feature which people can use if they like, but general facilities
should not require people use Org mode.

    2. Search for headlines matching a specific pattern. I found these
       patterns:

       - Keep a Changelog: [1.2.3] - 2026-07-30
       - Common Changelog: 1.2.3 - 2026-07-30
       - Towncrier:        1.2.3 (2026-07-30)
       - Magit style:      v1.2.3 2026-07-30

Could you explain what that list means?

I can understand the second part of each line, as an example of
formating of a version number and a date.  We could easily simply
adopt one and say package maintainers should all use it.  And I think
we could easily write a converter to that one.

But the first part of each line seems to refer to things
I have never heard of.  What does "Towncrier" mean?
What does "Common Changelog" mean?

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)