Consider adding releases, issues opened/closed, etc. to the News and Status Reports section of interlisp.org

[hjellinek]

If Hugo supports pulling from RSS feeds, we could add release, issue, and other GitHub-derived information to the News and Status Reports section of interlisp.org.

GitHub's commits feed looks like https://github.com/interlisp/medley/commits/master.atom.
The release feeds look like https://github.com/interlisp/medley/releases.atom.

[masinter]

I fear we haven't developed the habit of writing commit messages in a way that they will produce useful "what changed" summaries. There is scant feedback on what those release notes would look like.
Compared to the ease of changing the Lisp code to behave differently, the tools for documenting those changes are crude if there are any at all. While we might continue to produce "what's changed" notes, i don't think what we're getting now is particularly useful. The effort to editorially write a summary of changes every few months vs. fixing our commit messages.... @rmkaplan @fghalasz @masinter @stumbo @lispcore

on the other hand -- bug fixes and new Medley features aren't worth much without some minimal documentation in a consistent place.