What's new pages and release note - we have 4 different pages!

As I am creating the community handbooks, I noticed that we have several different pages where we document what's new in each release:

This is creating confusion even between regular contributors to the project (see @abbe98 comment here OpenRefine 3.7.9 released - #5 by abbe98) to get the latest information. I suspect this is also creating overhead when making a release.

Should we limit the number of pages to maintain? Which one should we keep?

Yes, let's streamline all that!
I propose to get rid of the "Whats New" page on the wiki, replacing it with a redirect to What's new | OpenRefine

Let's also switch to documenting the changes in each patch release independently instead of aggregating it per minor release.

I think it still makes sense to have release notes on the website (more publicly facing). Should the text in the GitHub releases redirect the reader to the website then? One thing to keep in mind is that GitHub relies on usernames in the text of the GitHub release to generate a list of release contributors, which is advertised as such in social media. So if the text is just a redirection, it will look as if the person publishing the release is the only contributor, which is not ideal.

So far I have been using the wiki as a place where to draft release notes - writing them takes quite a bit of time so it's helpful not to have to do that in one go, during the release.

1 Like

I agree that we can redirect the wiki page to the What's new on the website.

Intuitively, I would not separate the release note from the actual release and, therefore, rely on GitHub as the place to publish the release note. This way, we also keep GitHub native feature to list contributors in each release. The What's New page can list existing releases, provide a brief overview (similar to what is shared in the blog post?) and redirect to each GitHub release for the details.