Should we stop publishing changelogs to the nodejs.org website?

[MylesBorins]

https://github.com/nodejs/node/releases is already a canonical place to find the change logs and arguably has many of the features we might want on the blog such as an rss feed.

The primary difference right now is that we do not currently publish that shasums on the release page, but that can easily be rectified. We could also arguably work something into the release script / node-core-utils / github actions to automate the process of making the release entry that contains all the information.

Making this choice would also limit the scope of what needs to be done on nodejs.dev, we could potentially completely remove the blog from the scope of the new website

[MylesBorins]

/cc @nodejs/website

[nschonni]

One minor difference between the GitHub release feed (because I use the current one 😄 ) is that the current one also includes the download links. That's something that could be added to the GitHub releases if it's replacing the page.

One current case I'm not sure how it would work would be the way "security releases" are handled on the blog vs. an only GitHub release approach

[mhdawson]

we could potentially completely remove the blog from the scope of the new website

This would probably warrant broader discussion as I recently had a suggestion that using the website blog instead of medium might get more viewership.

[ruyadorno]

Also worth taking into account how disruptive that would be for readers that are used to reaching out to the current blog to get the changelogs for each release. (including me 😳)

[yoshuawuyts]

Perhaps it's worth taking a look at how other programming tools approach communication around releases. For example Rust publishes both a release blog post, and a detailed changelog entry in the rust-lang/rust RELEASES.md file.

The purpose of the blog post is to communicate noteworthy changes made in the latest release to the wider community. With the latter being a point-by-point list of every change made.

Node.js release notes are more sparse in comparison. This can make it hard to stay up to date on what's new, placing the burden on users to discover why they should care about the changes made. Rather than deprecating the web version of the release notes, I'd love for Node to instead use that opportunity to communicate in more depth about the changes in that release.

That way it no longer feels like a bunch of duplication between where releases are shared, and instead each can be more clearly tuned for a specific audience.

[targos]

@yoshuawuyts That's a good point, and something that's already been discussed before. In my opinion, the problem with Node.js release notes is not the medium, though. It's that we do not have good process to prepare them with the help of all collaborators before doing the actual release, so the job is entirely up to the releasers and they already have a lot to do.
I've been trying myself to create more user-friendly changelogs (example) and while I don't know if it has been successful, I think it is possible to use the same format in the blog posts and in the changelog files (People who are not interested in the detailed list can stop reading after the notable changes section).

[aduh95]

One thing to consider is that not everyone has access to GitHub (E.G.: people in Iran), while the website is open to everyone (I think, unless we have restrictions there too?).

[nickserv]

FWIW GitHub's restrictions against Iran are going away.

Source: Advancing developer freedom: GitHub is fully available in Iran

[BethGriggs]

Could this be closed? It's a fairly old issue and I do not believe we intend to stop publishing changelogs to the nodejs.org website.

(There are some enhancements mentioned in this thread, but I believe that's a separate topic likely covered by #568.)

[targos]

@MylesBorins how did you do that?